https://wiki.code4lib.org/api.php?action=feedcontributions&feedformat=atom&user=Ndushay 2026-04-08T20:15:05Z User contributions MediaWiki 1.26.2 https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42288 2014-12-08T19:20:47Z

<p>Ndushay: /* Linked Data Workshop */</p> <hr /> <div>== Preconference Schedule (draft) ==<br /> <br /> Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.<br /> <br /> This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br /> |-<br /> | '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp; possibly beyond (Needs: projector/screen)<br /> |-<br /> | '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) <br /> |-<br /> | '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp<br /> |-<br /> | '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)<br /> |-<br /> | '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)<br /> |-<br /> | '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br /> |-<br /> | '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)<br /> |-<br /> | '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker<br /> |-<br /> | '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)<br /> |-<br /> | '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)<br /> |-<br /> | '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)<br /> |}<br /> <br /> == Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conferences ==<br /> <br /> ===MORNING:===<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Laney McGlohon, Stanford University, laneymcg@stanford.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Chris Sharp<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Matt Critchlow<br /> # Ray Henry<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> # Barbara Hui<br /> # Carol Bean<br /> # Matt Connolly<br /> # James Van Mil<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> # Whitni Watkins<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> # Chris Sharp<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> # Mark Mounts<br /> # Heather Pitts<br /> # Andrew Woods<br /> # Carol Bean<br /> # Naomi Dushay (probably)<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> # Emily Lynema<br /> # Bret Davidson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> # Josh Wilson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CANCELLED: ''UXtravaganza'' ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> # Whitni Watkins (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> # Laurie Reeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Mounts<br /> # Kathryn Stine<br /> # Steve Meyer<br /> # Matt Critchlow<br /> # Andrew Pasterfield<br /> # Ray Henry<br /> # Bret Davidson<br /> # Naomi Dushay (maybe)<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Terry Brady<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Jarrell<br /> # Heather Pitts<br /> # Kathryn Stine<br /> # Andrew Woods<br /> <br /> [[Category:Code4Lib2015]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42287 2014-12-08T19:18:18Z

<p>Ndushay: /* Visualizing Library Data */</p> <hr /> <div>== Preconference Schedule (draft) ==<br /> <br /> Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.<br /> <br /> This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br /> |-<br /> | '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp; possibly beyond (Needs: projector/screen)<br /> |-<br /> | '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) <br /> |-<br /> | '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp<br /> |-<br /> | '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)<br /> |-<br /> | '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)<br /> |-<br /> | '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br /> |-<br /> | '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)<br /> |-<br /> | '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker<br /> |-<br /> | '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)<br /> |-<br /> | '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)<br /> |-<br /> | '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)<br /> |}<br /> <br /> == Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conferences ==<br /> <br /> ===MORNING:===<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Laney McGlohon, Stanford University, laneymcg@stanford.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Chris Sharp<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Matt Critchlow<br /> # Ray Henry<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> # Barbara Hui<br /> # Carol Bean<br /> # Matt Connolly<br /> # James Van Mil<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> # Whitni Watkins<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> # Chris Sharp<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> # Mark Mounts<br /> # Heather Pitts<br /> # Andrew Woods<br /> # Carol Bean<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> # Emily Lynema<br /> # Bret Davidson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> # Josh Wilson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CANCELLED: ''UXtravaganza'' ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> # Whitni Watkins (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> # Laurie Reeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Mounts<br /> # Kathryn Stine<br /> # Steve Meyer<br /> # Matt Critchlow<br /> # Andrew Pasterfield<br /> # Ray Henry<br /> # Bret Davidson<br /> # Naomi Dushay (maybe)<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Terry Brady<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Jarrell<br /> # Heather Pitts<br /> # Kathryn Stine<br /> # Andrew Woods<br /> <br /> [[Category:Code4Lib2015]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=41990 2014-11-07T19:49:47Z

<p>Ndushay: </p> <hr /> <div>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/. <br /> The conference will be held at the Portland Hilton &amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> We encourage everyone to propose a talk.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br /> * Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br /> * Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br /> * Technical issues - Big issues in library technology that should be addressed or better understood<br /> * 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.<br /> <br /> 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.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> 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.<br /> Provide a title and brief (500 words or fewer) description of your proposed talk.<br /> 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.<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Talk Title: ==<br /> <br /> * Speaker's name, email address, and (optional) affiliation<br /> * Second speaker's name, email address, and affiliation, if second speaker<br /> <br /> Abstract of no more than 500 words.<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Talk Proposals'''<br /> == Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br /> <br /> * [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]<br /> * [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br /> <br /> 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!<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Both games will be demoed.<br /> <br /> We have never presented at Code4lib.<br /> <br /> == Do the Semantic FRBRoo ==<br /> * Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br /> <br /> [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?<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> == Our $50,000 Problem: Why Library School? ==<br /> * Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br /> <br /> 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.]<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> * Rachel Wittmann, rwittma@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> In this talk, we will discuss:<br /> * Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br /> * The stumbling blocks experienced in that process and how they were resolved.<br /> * 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. <br /> * A brief overview of the export and import functions and also current workflow practices within Providence.<br /> * Future plans &amp; the role of CollectiveAccess at Clemson University Libraries<br /> <br /> == Getting ContentDM and Wordpress to Play Together ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br /> <br /> ==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br /> <br /> * [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br /> <br /> 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 &quot;topics&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.<br /> <br /> For more info check out http://www.docrefinery.org.<br /> <br /> ==Drupal 8 — Evolution &amp; Revolution==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br /> <br /> ==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br /> <br /> * [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br /> <br /> 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].<br /> <br /> ==The Impossible Search: Pulling data from multiple unknown sources==<br /> <br /> * Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br /> <br /> 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.<br /> <br /> ==What! You're Not Using Docker?==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> *[1]https://www.docker.com/<br /> <br /> == Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br /> <br /> * Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br /> <br /> 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.<br /> <br /> == Categorizing Records with Random Forests ==<br /> <br /> * Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br /> 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. <br /> <br /> == Data Science in Libraries ==<br /> <br /> * Devon Smith, smithde@oclc.org, OCLC<br /> <br /> 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.<br /> <br /> == PDF metadata extraction for academic literature == <br /> <br /> * Kevin Savage, kevin.savage at mendeley.com, Mendeley<br /> * Joyce Stack, joyce.stack at mendeley.com, Mendeley<br /> <br /> Mendeley recently added a, &quot;document from file,&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.<br /> <br /> == Giving Users What They Want: Record Grouping in VuFind ==<br /> <br /> * Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br /> <br /> 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.<br /> <br /> == Topic Space: a mobile augmented reality recommendation app ==<br /> <br /> * Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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].<br /> <br /> == Leveling Up Your Git Workflow ==<br /> <br /> * Megan Kudzia, moneill@albion.edu, Albion College Library<br /> * Kate Sears, eks11@albion.edu, Albion College Library<br /> <br /> 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).<br /> <br /> == Drone Loaning Program: Because Laptops are so last century ==<br /> <br /> * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br /> * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br /> <br /> 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 &quot;Is the drone available?&quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br /> <br /> == Got Git? Getting More Out of Your GitHub Repositories ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br /> <br /> 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!<br /> <br /> * [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br /> * [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br /> * [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br /> * [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br /> * Gists for code sharing<br /> * Private Repositories and Organizational Groups<br /> * Pull Request Conversation Tracking<br /> * Customized Issue management<br /> <br /> == Quick Wins for Every Department in the Library - File Analyzer! ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating COUNTER compliant reports for the Electronic Resources department<br /> * Generating ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br /> <br /> ==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br /> <br /> * [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br /> <br /> 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. <br /> <br /> == Building Your Own Federated Search ==<br /> <br /> * Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> == Indexing Linked Data with LDPath ==<br /> <br /> * Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> [1] http://marmotta.apache.org/ldpath/language.html<br /> <br /> == Show Me the Money: Integrating an LMS with Payment Providers ==<br /> <br /> * Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br /> <br /> 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.<br /> <br /> == Shibboleth Federated Authentication for Library Applications: ==<br /> <br /> * Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br /> * Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br /> <br /> 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.<br /> <br /> ==Scientific Data: A Needs Assessment Journey==<br /> <br /> *[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> 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;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. <br /> <br /> == Feminist Human Computer Interaction (HCI) in Library Software ==<br /> <br /> * Bess Sadler, bess@stanford.edu, Stanford University Libraries<br /> <br /> 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. <br /> <br /> [1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br /> <br /> [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<br /> <br /> == Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br /> <br /> * Audrey Altman, audrey at dp.la, Digital Public Library of America<br /> * Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br /> * Mark Breedlove, mb at dp.la, Digital Public Library of America<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> == OS or GTFO: Program or Perish ==<br /> *Tessa Fallon, tessa.fallon@gmail.com<br /> <br /> Description TBD<br /> <br /> == Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br /> * Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br /> 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.<br /> <br /> == REPOX: Metadata Blender ==<br /> <br /> * John Mignault, jmignault@metro.org, Empire State Digital Network<br /> <br /> 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.<br /> <br /> == Beyond Open Source ==<br /> <br /> * Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br /> * Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> [[Category:Code4Lib2015]] <br /> [[Category:Talk Proposals]]<br /> <br /> == Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br /> <br /> * Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br /> * Max King, mking9@iit.edu, Illinois Institute of Technology<br /> <br /> 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.<br /> 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.<br /> 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.<br /> <br /> == Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br /> <br /> * Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br /> <br /> * Jefferson Bailey, jefferson@archive.org, Internet Archive<br /> * Vinay Goel, vinay@archive.org, Internet Archive<br /> <br /> 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.<br /> <br /> == Awesome Pi, LOL! ==<br /> <br /> * Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br /> * Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br /> <br /> 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.<br /> <br /> == You Gotta Keep 'em Separated: The Case for &quot;Bento Box&quot; Discovery Interfaces ==<br /> <br /> * Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br /> <br /> I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br /> <br /> 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.<br /> <br /> Now, the question is, for your &quot;everything&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?<br /> <br /> At UNT, we've been holding off on implementing an &quot;everything&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.<br /> <br /> 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 &quot;everything&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.<br /> <br /> 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 &quot;bento box&quot; discovery bandwagon and why I think &quot;bento box&quot; is at this point the path that least sells our souls.<br /> <br /> == Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br /> <br /> * Ashley Blewer!, ashley.blewer@gmail.com<br /> <br /> 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?<br /> <br /> == Level Up Your Coding with Code Club (yes, you can talk about it) ==<br /> <br /> * Coral Sheldon-Hess, coral@sheldon-hess.org<br /> <br /> 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.<br /> <br /> But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br /> <br /> 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! <br /> <br /> == The Growth of a Programmer ==<br /> <br /> * [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br /> <br /> 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.<br /> <br /> == Developing a Fedora 4.0 Content Model for Disk Images ==<br /> <br /> * Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br /> * Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br /> <br /> 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.<br /> <br /> == Data acquisition and publishing tools in R ==<br /> <br /> * Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br /> <br /> 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).<br /> <br /> == SPLUNK: Log File Analysis ==<br /> <br /> * Jim LeFager, jlefager@depaul.edu, DePaul University Library<br /> 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. <br /> <br /> == Your code does not exist in a vacuum ==<br /> * Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br /> <br /> “If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br /> <br /> * Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br /> * Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> http://chicagocollectionsconsortium.org<br /> <br /> == Programmers are not projects: lessons learned from managing humans ==<br /> <br /> * Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br /> <br /> 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.<br /> <br /> == Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br /> <br /> * Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br /> <br /> 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? <br /> <br /> 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.<br /> <br /> == A Semantic Makeover for CMS Data ==<br /> <br /> * Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br /> <br /> 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.<br /> <br /> == Taking User Experience (UX) to new heights ==<br /> <br /> * Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br /> <br /> User Experience, or &quot;UX&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:<br /> <br /> - 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.<br /> <br /> - Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &quot;heat maps&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.<br /> <br /> - Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br /> <br /> 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.<br /> <br /> ==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br /> <br /> *Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br /> *Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br /> *May Yan, Ryerson University, may.yan@ryerson.ca<br /> <br /> 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. <br /> <br /> 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: <br /> “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.” <br /> <br /> 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.<br /> <br /> ==Making your digital objects embeddable around the web==<br /> <br /> * Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==So you want to make your geospatial data discoverable==<br /> <br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> == Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br /> <br /> * Adam Wead, awead@psu.edu, Penn State University<br /> <br /> Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br /> Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br /> wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br /> Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br /> tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br /> working solution that exhibited all the hallmarks of good testing and software design.<br /> <br /> This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br /> You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br /> problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br /> viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br /> development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br /> to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br /> <br /> <br /> == Designing and Leading a Kick A** Tech Team ==<br /> <br /> * Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br /> <br /> 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.<br /> <br /> <br /> ==American (Archives) Horror Story: LTO Failure and Data Loss ==<br /> <br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> <br /> 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!<br /> <br /> == PBCore in Action: Three Words, Not Two! ==<br /> <br /> * Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> * Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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<br /> <br /> <br /> ==Collaborating to Avert the Digital Graveyard==<br /> <br /> * Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br /> * Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br /> <br /> 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. <br /> <br /> 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.<br /> <br /> ==Docker? VMs? EC2? Yes! With Packer.io==<br /> <br /> * Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br /> <br /> 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!<br /> <br /> == Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br /> <br /> * [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)<br /> <br /> 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.<br /> <br /> 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 &quot;nearest branch to my current location&quot; functionality to this app.<br /> <br /> Despite the &quot;development phase&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.<br /> <br /> This talk will explore the following questions:<br /> <br /> * 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.<br /> <br /> * 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.)<br /> <br /> * 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.<br /> <br /> * 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.”<br /> <br /> * 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.<br /> <br /> ==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br /> <br /> * Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br /> * Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br /> <br /> We have to &quot;turn projects into programs&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?<br /> <br /> 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!<br /> <br /> == Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br /> <br /> * Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Helping Google (and scholars, researchers, educators, &amp; the public) find archival audio ==<br /> <br /> * Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)<br /> <br /> 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:<br /> <br /> Audio is opaque: you can’t picture sound, or skim the words in a recording. <br /> Audio is hard to share: there’s no text to interact with. <br /> Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.<br /> Audio metadata is inconsistent and incomplete.<br /> <br /> 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.<br /> <br /> == Digital Content Integrated with ILS Data for User Discovery: Lessons Learned ==<br /> <br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> * Laney McGlohon, laneymcg@stanford.edu, Stanford University Libraries<br /> <br /> 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?<br /> <br /> At Stanford, we have these cases and more:<br /> * digital content with no metadata in ILS<br /> * digital content for metadata in ILS<br /> * digital content with its own metadata derived from ILS metadata.<br /> <br /> 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.</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=41986 2014-11-07T19:21:28Z

<p>Ndushay: </p> <hr /> <div>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/. <br /> The conference will be held at the Portland Hilton &amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> We encourage everyone to propose a talk.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br /> * Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br /> * Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br /> * Technical issues - Big issues in library technology that should be addressed or better understood<br /> * 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.<br /> <br /> 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.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> 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.<br /> Provide a title and brief (500 words or fewer) description of your proposed talk.<br /> 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.<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Talk Title: ==<br /> <br /> * Speaker's name, email address, and (optional) affiliation<br /> * Second speaker's name, email address, and affiliation, if second speaker<br /> <br /> Abstract of no more than 500 words.<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Talk Proposals'''<br /> == Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br /> <br /> * [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]<br /> * [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br /> <br /> 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!<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Both games will be demoed.<br /> <br /> We have never presented at Code4lib.<br /> <br /> == Do the Semantic FRBRoo ==<br /> * Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br /> <br /> [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?<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> == Our $50,000 Problem: Why Library School? ==<br /> * Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br /> <br /> 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.]<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> * Rachel Wittmann, rwittma@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> In this talk, we will discuss:<br /> * Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br /> * The stumbling blocks experienced in that process and how they were resolved.<br /> * 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. <br /> * A brief overview of the export and import functions and also current workflow practices within Providence.<br /> * Future plans &amp; the role of CollectiveAccess at Clemson University Libraries<br /> <br /> == Getting ContentDM and Wordpress to Play Together ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br /> <br /> ==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br /> <br /> * [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br /> <br /> 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 &quot;topics&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.<br /> <br /> For more info check out http://www.docrefinery.org.<br /> <br /> ==Drupal 8 — Evolution &amp; Revolution==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br /> <br /> ==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br /> <br /> * [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br /> <br /> 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].<br /> <br /> ==The Impossible Search: Pulling data from multiple unknown sources==<br /> <br /> * Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br /> <br /> 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.<br /> <br /> ==What! You're Not Using Docker?==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> *[1]https://www.docker.com/<br /> <br /> == Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br /> <br /> * Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br /> <br /> 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.<br /> <br /> == Categorizing Records with Random Forests ==<br /> <br /> * Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br /> 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. <br /> <br /> == Data Science in Libraries ==<br /> <br /> * Devon Smith, smithde@oclc.org, OCLC<br /> <br /> 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.<br /> <br /> == PDF metadata extraction for academic literature == <br /> <br /> * Kevin Savage, kevin.savage at mendeley.com, Mendeley<br /> * Joyce Stack, joyce.stack at mendeley.com, Mendeley<br /> <br /> Mendeley recently added a, &quot;document from file,&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.<br /> <br /> == Giving Users What They Want: Record Grouping in VuFind ==<br /> <br /> * Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br /> <br /> 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.<br /> <br /> == Topic Space: a mobile augmented reality recommendation app ==<br /> <br /> * Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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].<br /> <br /> == Leveling Up Your Git Workflow ==<br /> <br /> * Megan Kudzia, moneill@albion.edu, Albion College Library<br /> * Kate Sears, eks11@albion.edu, Albion College Library<br /> <br /> 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).<br /> <br /> == Drone Loaning Program: Because Laptops are so last century ==<br /> <br /> * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br /> * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br /> <br /> 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 &quot;Is the drone available?&quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br /> <br /> == Got Git? Getting More Out of Your GitHub Repositories ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br /> <br /> 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!<br /> <br /> * [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br /> * [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br /> * [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br /> * [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br /> * Gists for code sharing<br /> * Private Repositories and Organizational Groups<br /> * Pull Request Conversation Tracking<br /> * Customized Issue management<br /> <br /> == Quick Wins for Every Department in the Library - File Analyzer! ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating COUNTER compliant reports for the Electronic Resources department<br /> * Generating ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br /> <br /> ==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br /> <br /> * [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br /> <br /> 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. <br /> <br /> == Building Your Own Federated Search ==<br /> <br /> * Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> == Indexing Linked Data with LDPath ==<br /> <br /> * Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> [1] http://marmotta.apache.org/ldpath/language.html<br /> <br /> == Show Me the Money: Integrating an LMS with Payment Providers ==<br /> <br /> * Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br /> <br /> 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.<br /> <br /> == Shibboleth Federated Authentication for Library Applications: ==<br /> <br /> * Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br /> * Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br /> <br /> 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.<br /> <br /> ==Scientific Data: A Needs Assessment Journey==<br /> <br /> *[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> 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;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. <br /> <br /> == Feminist Human Computer Interaction (HCI) in Library Software ==<br /> <br /> * Bess Sadler, bess@stanford.edu, Stanford University Libraries<br /> <br /> 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. <br /> <br /> [1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br /> <br /> [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<br /> <br /> == Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br /> <br /> * Audrey Altman, audrey at dp.la, Digital Public Library of America<br /> * Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br /> * Mark Breedlove, mb at dp.la, Digital Public Library of America<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> == OS or GTFO: Program or Perish ==<br /> *Tessa Fallon, tessa.fallon@gmail.com<br /> <br /> Description TBD<br /> <br /> == Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br /> * Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br /> 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.<br /> <br /> == REPOX: Metadata Blender ==<br /> <br /> * John Mignault, jmignault@metro.org, Empire State Digital Network<br /> <br /> 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.<br /> <br /> == Beyond Open Source ==<br /> <br /> * Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br /> * Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> [[Category:Code4Lib2015]] <br /> [[Category:Talk Proposals]]<br /> <br /> == Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br /> <br /> * Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br /> * Max King, mking9@iit.edu, Illinois Institute of Technology<br /> <br /> 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.<br /> 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.<br /> 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.<br /> <br /> == Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br /> <br /> * Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br /> <br /> * Jefferson Bailey, jefferson@archive.org, Internet Archive<br /> * Vinay Goel, vinay@archive.org, Internet Archive<br /> <br /> 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.<br /> <br /> == Awesome Pi, LOL! ==<br /> <br /> * Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br /> * Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br /> <br /> 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.<br /> <br /> == You Gotta Keep 'em Separated: The Case for &quot;Bento Box&quot; Discovery Interfaces ==<br /> <br /> * Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br /> <br /> I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br /> <br /> 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.<br /> <br /> Now, the question is, for your &quot;everything&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?<br /> <br /> At UNT, we've been holding off on implementing an &quot;everything&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.<br /> <br /> 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 &quot;everything&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.<br /> <br /> 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 &quot;bento box&quot; discovery bandwagon and why I think &quot;bento box&quot; is at this point the path that least sells our souls.<br /> <br /> == Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br /> <br /> * Ashley Blewer!, ashley.blewer@gmail.com<br /> <br /> 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?<br /> <br /> == Level Up Your Coding with Code Club (yes, you can talk about it) ==<br /> <br /> * Coral Sheldon-Hess, coral@sheldon-hess.org<br /> <br /> 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.<br /> <br /> But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br /> <br /> 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! <br /> <br /> == The Growth of a Programmer ==<br /> <br /> * [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br /> <br /> 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.<br /> <br /> == Developing a Fedora 4.0 Content Model for Disk Images ==<br /> <br /> * Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br /> * Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br /> <br /> 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.<br /> <br /> == Data acquisition and publishing tools in R ==<br /> <br /> * Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br /> <br /> 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).<br /> <br /> == SPLUNK: Log File Analysis ==<br /> <br /> * Jim LeFager, jlefager@depaul.edu, DePaul University Library<br /> 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. <br /> <br /> == Your code does not exist in a vacuum ==<br /> * Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br /> <br /> “If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br /> <br /> * Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br /> * Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> http://chicagocollectionsconsortium.org<br /> <br /> == Programmers are not projects: lessons learned from managing humans ==<br /> <br /> * Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br /> <br /> 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.<br /> <br /> == Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br /> <br /> * Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br /> <br /> 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? <br /> <br /> 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.<br /> <br /> == A Semantic Makeover for CMS Data ==<br /> <br /> * Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br /> <br /> 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.<br /> <br /> == Taking User Experience (UX) to new heights ==<br /> <br /> * Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br /> <br /> User Experience, or &quot;UX&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:<br /> <br /> - 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.<br /> <br /> - Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &quot;heat maps&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.<br /> <br /> - Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br /> <br /> 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.<br /> <br /> ==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br /> <br /> *Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br /> *Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br /> *May Yan, Ryerson University, may.yan@ryerson.ca<br /> <br /> 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. <br /> <br /> 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: <br /> “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.” <br /> <br /> 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.<br /> <br /> ==Making your digital objects embeddable around the web==<br /> <br /> * Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==So you want to make your geospatial data discoverable==<br /> <br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> == Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br /> <br /> * Adam Wead, awead@psu.edu, Penn State University<br /> <br /> Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br /> Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br /> wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br /> Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br /> tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br /> working solution that exhibited all the hallmarks of good testing and software design.<br /> <br /> This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br /> You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br /> problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br /> viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br /> development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br /> to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br /> <br /> <br /> == Designing and Leading a Kick A** Tech Team ==<br /> <br /> * Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br /> <br /> 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.<br /> <br /> <br /> ==American (Archives) Horror Story: LTO Failure and Data Loss ==<br /> <br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> <br /> 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!<br /> <br /> == PBCore in Action: Three Words, Not Two! ==<br /> <br /> * Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> * Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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<br /> <br /> <br /> ==Collaborating to Avert the Digital Graveyard==<br /> <br /> * Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br /> * Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br /> <br /> 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. <br /> <br /> 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.<br /> <br /> ==Docker? VMs? EC2? Yes! With Packer.io==<br /> <br /> * Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br /> <br /> 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!<br /> <br /> == Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br /> <br /> * [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)<br /> <br /> 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.<br /> <br /> 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 &quot;nearest branch to my current location&quot; functionality to this app.<br /> <br /> Despite the &quot;development phase&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.<br /> <br /> This talk will explore the following questions:<br /> <br /> * 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.<br /> <br /> * 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.)<br /> <br /> * 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.<br /> <br /> * 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.”<br /> <br /> * 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.<br /> <br /> ==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br /> <br /> * Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br /> * Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br /> <br /> We have to &quot;turn projects into programs&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?<br /> <br /> 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!<br /> <br /> == Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br /> <br /> * Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=41985 2014-11-07T19:17:50Z

<p>Ndushay: /* Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) */</p> <hr /> <div>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/. <br /> The conference will be held at the Portland Hilton &amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> We encourage everyone to propose a talk.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br /> * Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br /> * Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br /> * Technical issues - Big issues in library technology that should be addressed or better understood<br /> * 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.<br /> <br /> 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.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> 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.<br /> Provide a title and brief (500 words or fewer) description of your proposed talk.<br /> 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.<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Talk Title: ==<br /> <br /> * Speaker's name, email address, and (optional) affiliation<br /> * Second speaker's name, email address, and affiliation, if second speaker<br /> <br /> Abstract of no more than 500 words.<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Talk Proposals'''<br /> == Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br /> <br /> * [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]<br /> * [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br /> <br /> 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!<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Both games will be demoed.<br /> <br /> We have never presented at Code4lib.<br /> <br /> == Do the Semantic FRBRoo ==<br /> * Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br /> <br /> [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?<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> == Our $50,000 Problem: Why Library School? ==<br /> * Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br /> <br /> 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.]<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> * Rachel Wittmann, rwittma@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> In this talk, we will discuss:<br /> * Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br /> * The stumbling blocks experienced in that process and how they were resolved.<br /> * 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. <br /> * A brief overview of the export and import functions and also current workflow practices within Providence.<br /> * Future plans &amp; the role of CollectiveAccess at Clemson University Libraries<br /> <br /> == Getting ContentDM and Wordpress to Play Together ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br /> <br /> ==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br /> <br /> * [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br /> <br /> 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 &quot;topics&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.<br /> <br /> For more info check out http://www.docrefinery.org.<br /> <br /> ==Drupal 8 — Evolution &amp; Revolution==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br /> <br /> ==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br /> <br /> * [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br /> <br /> 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].<br /> <br /> ==The Impossible Search: Pulling data from multiple unknown sources==<br /> <br /> * Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br /> <br /> 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.<br /> <br /> ==What! You're Not Using Docker?==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> *[1]https://www.docker.com/<br /> <br /> == Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br /> <br /> * Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br /> <br /> 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.<br /> <br /> == Categorizing Records with Random Forests ==<br /> <br /> * Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br /> 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. <br /> <br /> == Data Science in Libraries ==<br /> <br /> * Devon Smith, smithde@oclc.org, OCLC<br /> <br /> 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.<br /> <br /> == PDF metadata extraction for academic literature == <br /> <br /> * Kevin Savage, kevin.savage at mendeley.com, Mendeley<br /> * Joyce Stack, joyce.stack at mendeley.com, Mendeley<br /> <br /> Mendeley recently added a, &quot;document from file,&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.<br /> <br /> == Giving Users What They Want: Record Grouping in VuFind ==<br /> <br /> * Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br /> <br /> 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.<br /> <br /> == Topic Space: a mobile augmented reality recommendation app ==<br /> <br /> * Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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].<br /> <br /> == Leveling Up Your Git Workflow ==<br /> <br /> * Megan Kudzia, moneill@albion.edu, Albion College Library<br /> * Kate Sears, eks11@albion.edu, Albion College Library<br /> <br /> 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).<br /> <br /> == Drone Loaning Program: Because Laptops are so last century ==<br /> <br /> * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br /> * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br /> <br /> 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 &quot;Is the drone available?&quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br /> <br /> == Got Git? Getting More Out of Your GitHub Repositories ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br /> <br /> 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!<br /> <br /> * [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br /> * [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br /> * [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br /> * [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br /> * Gists for code sharing<br /> * Private Repositories and Organizational Groups<br /> * Pull Request Conversation Tracking<br /> * Customized Issue management<br /> <br /> == Quick Wins for Every Department in the Library - File Analyzer! ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating COUNTER compliant reports for the Electronic Resources department<br /> * Generating ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br /> <br /> ==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br /> <br /> * [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br /> <br /> 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. <br /> <br /> == Building Your Own Federated Search ==<br /> <br /> * Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> == Indexing Linked Data with LDPath ==<br /> <br /> * Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> [1] http://marmotta.apache.org/ldpath/language.html<br /> <br /> == Show Me the Money: Integrating an LMS with Payment Providers ==<br /> <br /> * Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br /> <br /> 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.<br /> <br /> == Shibboleth Federated Authentication for Library Applications: ==<br /> <br /> * Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br /> * Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br /> <br /> 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.<br /> <br /> ==Scientific Data: A Needs Assessment Journey==<br /> <br /> *[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> 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;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. <br /> <br /> == Feminist Human Computer Interaction (HCI) in Library Software ==<br /> <br /> * Bess Sadler, bess@stanford.edu, Stanford University Libraries<br /> <br /> 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. <br /> <br /> [1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br /> <br /> [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<br /> <br /> == Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br /> <br /> * Audrey Altman, audrey at dp.la, Digital Public Library of America<br /> * Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br /> * Mark Breedlove, mb at dp.la, Digital Public Library of America<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> == OS or GTFO: Program or Perish ==<br /> *Tessa Fallon, tessa.fallon@gmail.com<br /> <br /> Description TBD<br /> <br /> == Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br /> * Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br /> 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.<br /> <br /> == REPOX: Metadata Blender ==<br /> <br /> * John Mignault, jmignault@metro.org, Empire State Digital Network<br /> <br /> 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.<br /> <br /> == Beyond Open Source ==<br /> <br /> * Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br /> * Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> [[Category:Code4Lib2015]] <br /> [[Category:Talk Proposals]]<br /> <br /> == Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br /> <br /> * Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br /> * Max King, mking9@iit.edu, Illinois Institute of Technology<br /> <br /> 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.<br /> 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.<br /> 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.<br /> <br /> == Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br /> <br /> * Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br /> <br /> * Jefferson Bailey, jefferson@archive.org, Internet Archive<br /> * Vinay Goel, vinay@archive.org, Internet Archive<br /> <br /> 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.<br /> <br /> == Awesome Pi, LOL! ==<br /> <br /> * Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br /> * Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br /> <br /> 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.<br /> <br /> == You Gotta Keep 'em Separated: The Case for &quot;Bento Box&quot; Discovery Interfaces ==<br /> <br /> * Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br /> <br /> I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br /> <br /> 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.<br /> <br /> Now, the question is, for your &quot;everything&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?<br /> <br /> At UNT, we've been holding off on implementing an &quot;everything&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.<br /> <br /> 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 &quot;everything&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.<br /> <br /> 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 &quot;bento box&quot; discovery bandwagon and why I think &quot;bento box&quot; is at this point the path that least sells our souls.<br /> <br /> == Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br /> <br /> * Ashley Blewer!, ashley.blewer@gmail.com<br /> <br /> 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?<br /> <br /> == Level Up Your Coding with Code Club (yes, you can talk about it) ==<br /> <br /> * Coral Sheldon-Hess, coral@sheldon-hess.org<br /> <br /> 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.<br /> <br /> But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br /> <br /> 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! <br /> <br /> == The Growth of a Programmer ==<br /> <br /> * [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br /> <br /> 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.<br /> <br /> == Developing a Fedora 4.0 Content Model for Disk Images ==<br /> <br /> * Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br /> * Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br /> <br /> 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.<br /> <br /> == Data acquisition and publishing tools in R ==<br /> <br /> * Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br /> <br /> 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).<br /> <br /> == SPLUNK: Log File Analysis ==<br /> <br /> * Jim LeFager, jlefager@depaul.edu, DePaul University Library<br /> 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. <br /> <br /> == Your code does not exist in a vacuum ==<br /> * Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br /> <br /> “If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br /> <br /> * Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br /> * Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> http://chicagocollectionsconsortium.org<br /> <br /> == Programmers are not projects: lessons learned from managing humans ==<br /> <br /> * Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br /> <br /> 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.<br /> <br /> == Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br /> <br /> * Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br /> <br /> 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? <br /> <br /> 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.<br /> <br /> == A Semantic Makeover for CMS Data ==<br /> <br /> * Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br /> <br /> 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.<br /> <br /> == Taking User Experience (UX) to new heights ==<br /> <br /> * Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br /> <br /> User Experience, or &quot;UX&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:<br /> <br /> - 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.<br /> <br /> - Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &quot;heat maps&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.<br /> <br /> - Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br /> <br /> 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.<br /> <br /> ==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br /> <br /> *Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br /> *Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br /> *May Yan, Ryerson University, may.yan@ryerson.ca<br /> <br /> 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. <br /> <br /> 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: <br /> “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.” <br /> <br /> 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.<br /> <br /> ==Making your digital objects embeddable around the web==<br /> <br /> * Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==So you want to make your geospatial data discoverable==<br /> <br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> == Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br /> <br /> * Adam Wead, awead@psu.edu, Penn State University<br /> <br /> Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br /> Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br /> wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br /> Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br /> tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br /> working solution that exhibited all the hallmarks of good testing and software design.<br /> <br /> This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br /> You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br /> problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br /> viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br /> development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br /> to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br /> <br /> <br /> == Designing and Leading a Kick A** Tech Team ==<br /> <br /> * Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br /> <br /> 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.<br /> <br /> <br /> ==American (Archives) Horror Story: LTO Failure and Data Loss ==<br /> <br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> <br /> 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!<br /> <br /> == PBCore in Action: Three Words, Not Two! ==<br /> <br /> * Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> * Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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<br /> <br /> <br /> ==Collaborating to Avert the Digital Graveyard==<br /> <br /> * Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br /> * Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br /> <br /> 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. <br /> <br /> 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.<br /> <br /> ==Docker? VMs? EC2? Yes! With Packer.io==<br /> <br /> * Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br /> <br /> 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!<br /> <br /> == Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br /> <br /> * [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)<br /> <br /> 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.<br /> <br /> 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 &quot;nearest branch to my current location&quot; functionality to this app.<br /> <br /> Despite the &quot;development phase&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.<br /> <br /> This talk will explore the following questions:<br /> <br /> * 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.<br /> <br /> * 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.)<br /> <br /> * 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.<br /> <br /> * 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.”<br /> <br /> * 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.<br /> <br /> ==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br /> <br /> * Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br /> * Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br /> <br /> We have to &quot;turn projects into programs&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?<br /> <br /> 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!<br /> <br /> == Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br /> <br /> * Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> <br /> Annotations on content resources allow users to contribute knowledge within the digital repository space. 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 and servers can be mixed and matched.<br /> <br /> 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.</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=41984 2014-11-07T19:12:55Z

<p>Ndushay: /* Annotations as Linked Data with Fedora4 and Triannon */</p> <hr /> <div>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/. <br /> The conference will be held at the Portland Hilton &amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> We encourage everyone to propose a talk.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br /> * Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br /> * Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br /> * Technical issues - Big issues in library technology that should be addressed or better understood<br /> * 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.<br /> <br /> 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.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> 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.<br /> Provide a title and brief (500 words or fewer) description of your proposed talk.<br /> 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.<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Talk Title: ==<br /> <br /> * Speaker's name, email address, and (optional) affiliation<br /> * Second speaker's name, email address, and affiliation, if second speaker<br /> <br /> Abstract of no more than 500 words.<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Talk Proposals'''<br /> == Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br /> <br /> * [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]<br /> * [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br /> <br /> 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!<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Both games will be demoed.<br /> <br /> We have never presented at Code4lib.<br /> <br /> == Do the Semantic FRBRoo ==<br /> * Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br /> <br /> [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?<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> == Our $50,000 Problem: Why Library School? ==<br /> * Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br /> <br /> 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.]<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> * Rachel Wittmann, rwittma@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> In this talk, we will discuss:<br /> * Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br /> * The stumbling blocks experienced in that process and how they were resolved.<br /> * 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. <br /> * A brief overview of the export and import functions and also current workflow practices within Providence.<br /> * Future plans &amp; the role of CollectiveAccess at Clemson University Libraries<br /> <br /> == Getting ContentDM and Wordpress to Play Together ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br /> <br /> ==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br /> <br /> * [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br /> <br /> 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 &quot;topics&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.<br /> <br /> For more info check out http://www.docrefinery.org.<br /> <br /> ==Drupal 8 — Evolution &amp; Revolution==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br /> <br /> ==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br /> <br /> * [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br /> <br /> 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].<br /> <br /> ==The Impossible Search: Pulling data from multiple unknown sources==<br /> <br /> * Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br /> <br /> 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.<br /> <br /> ==What! You're Not Using Docker?==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> *[1]https://www.docker.com/<br /> <br /> == Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br /> <br /> * Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br /> <br /> 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.<br /> <br /> == Categorizing Records with Random Forests ==<br /> <br /> * Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br /> 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. <br /> <br /> == Data Science in Libraries ==<br /> <br /> * Devon Smith, smithde@oclc.org, OCLC<br /> <br /> 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.<br /> <br /> == PDF metadata extraction for academic literature == <br /> <br /> * Kevin Savage, kevin.savage at mendeley.com, Mendeley<br /> * Joyce Stack, joyce.stack at mendeley.com, Mendeley<br /> <br /> Mendeley recently added a, &quot;document from file,&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.<br /> <br /> == Giving Users What They Want: Record Grouping in VuFind ==<br /> <br /> * Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br /> <br /> 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.<br /> <br /> == Topic Space: a mobile augmented reality recommendation app ==<br /> <br /> * Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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].<br /> <br /> == Leveling Up Your Git Workflow ==<br /> <br /> * Megan Kudzia, moneill@albion.edu, Albion College Library<br /> * Kate Sears, eks11@albion.edu, Albion College Library<br /> <br /> 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).<br /> <br /> == Drone Loaning Program: Because Laptops are so last century ==<br /> <br /> * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br /> * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br /> <br /> 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 &quot;Is the drone available?&quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br /> <br /> == Got Git? Getting More Out of Your GitHub Repositories ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br /> <br /> 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!<br /> <br /> * [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br /> * [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br /> * [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br /> * [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br /> * Gists for code sharing<br /> * Private Repositories and Organizational Groups<br /> * Pull Request Conversation Tracking<br /> * Customized Issue management<br /> <br /> == Quick Wins for Every Department in the Library - File Analyzer! ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating COUNTER compliant reports for the Electronic Resources department<br /> * Generating ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br /> <br /> ==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br /> <br /> * [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br /> <br /> 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. <br /> <br /> == Building Your Own Federated Search ==<br /> <br /> * Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> == Indexing Linked Data with LDPath ==<br /> <br /> * Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> [1] http://marmotta.apache.org/ldpath/language.html<br /> <br /> == Show Me the Money: Integrating an LMS with Payment Providers ==<br /> <br /> * Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br /> <br /> 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.<br /> <br /> == Shibboleth Federated Authentication for Library Applications: ==<br /> <br /> * Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br /> * Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br /> <br /> 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.<br /> <br /> ==Scientific Data: A Needs Assessment Journey==<br /> <br /> *[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> 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;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. <br /> <br /> == Feminist Human Computer Interaction (HCI) in Library Software ==<br /> <br /> * Bess Sadler, bess@stanford.edu, Stanford University Libraries<br /> <br /> 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. <br /> <br /> [1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br /> <br /> [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<br /> <br /> == Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br /> <br /> * Audrey Altman, audrey at dp.la, Digital Public Library of America<br /> * Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br /> * Mark Breedlove, mb at dp.la, Digital Public Library of America<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> == OS or GTFO: Program or Perish ==<br /> *Tessa Fallon, tessa.fallon@gmail.com<br /> <br /> Description TBD<br /> <br /> == Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br /> * Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br /> 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.<br /> <br /> == REPOX: Metadata Blender ==<br /> <br /> * John Mignault, jmignault@metro.org, Empire State Digital Network<br /> <br /> 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.<br /> <br /> == Beyond Open Source ==<br /> <br /> * Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br /> * Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> [[Category:Code4Lib2015]] <br /> [[Category:Talk Proposals]]<br /> <br /> == Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br /> <br /> * Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br /> * Max King, mking9@iit.edu, Illinois Institute of Technology<br /> <br /> 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.<br /> 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.<br /> 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.<br /> <br /> == Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br /> <br /> * Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br /> <br /> * Jefferson Bailey, jefferson@archive.org, Internet Archive<br /> * Vinay Goel, vinay@archive.org, Internet Archive<br /> <br /> 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.<br /> <br /> == Awesome Pi, LOL! ==<br /> <br /> * Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br /> * Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br /> <br /> 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.<br /> <br /> == You Gotta Keep 'em Separated: The Case for &quot;Bento Box&quot; Discovery Interfaces ==<br /> <br /> * Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br /> <br /> I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br /> <br /> 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.<br /> <br /> Now, the question is, for your &quot;everything&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?<br /> <br /> At UNT, we've been holding off on implementing an &quot;everything&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.<br /> <br /> 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 &quot;everything&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.<br /> <br /> 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 &quot;bento box&quot; discovery bandwagon and why I think &quot;bento box&quot; is at this point the path that least sells our souls.<br /> <br /> == Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br /> <br /> * Ashley Blewer!, ashley.blewer@gmail.com<br /> <br /> 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?<br /> <br /> == Level Up Your Coding with Code Club (yes, you can talk about it) ==<br /> <br /> * Coral Sheldon-Hess, coral@sheldon-hess.org<br /> <br /> 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.<br /> <br /> But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br /> <br /> 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! <br /> <br /> == The Growth of a Programmer ==<br /> <br /> * [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br /> <br /> 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.<br /> <br /> == Developing a Fedora 4.0 Content Model for Disk Images ==<br /> <br /> * Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br /> * Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br /> <br /> 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.<br /> <br /> == Data acquisition and publishing tools in R ==<br /> <br /> * Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br /> <br /> 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).<br /> <br /> == SPLUNK: Log File Analysis ==<br /> <br /> * Jim LeFager, jlefager@depaul.edu, DePaul University Library<br /> 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. <br /> <br /> == Your code does not exist in a vacuum ==<br /> * Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br /> <br /> “If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br /> <br /> * Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br /> * Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> http://chicagocollectionsconsortium.org<br /> <br /> == Programmers are not projects: lessons learned from managing humans ==<br /> <br /> * Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br /> <br /> 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.<br /> <br /> == Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br /> <br /> * Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br /> <br /> 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? <br /> <br /> 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.<br /> <br /> == A Semantic Makeover for CMS Data ==<br /> <br /> * Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br /> <br /> 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.<br /> <br /> == Taking User Experience (UX) to new heights ==<br /> <br /> * Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br /> <br /> User Experience, or &quot;UX&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:<br /> <br /> - 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.<br /> <br /> - Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &quot;heat maps&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.<br /> <br /> - Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br /> <br /> 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.<br /> <br /> ==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br /> <br /> *Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br /> *Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br /> *May Yan, Ryerson University, may.yan@ryerson.ca<br /> <br /> 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. <br /> <br /> 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: <br /> “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.” <br /> <br /> 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.<br /> <br /> ==Making your digital objects embeddable around the web==<br /> <br /> * Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==So you want to make your geospatial data discoverable==<br /> <br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> == Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br /> <br /> * Adam Wead, awead@psu.edu, Penn State University<br /> <br /> Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br /> Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br /> wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br /> Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br /> tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br /> working solution that exhibited all the hallmarks of good testing and software design.<br /> <br /> This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br /> You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br /> problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br /> viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br /> development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br /> to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br /> <br /> <br /> == Designing and Leading a Kick A** Tech Team ==<br /> <br /> * Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br /> <br /> 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.<br /> <br /> <br /> ==American (Archives) Horror Story: LTO Failure and Data Loss ==<br /> <br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> <br /> 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!<br /> <br /> == PBCore in Action: Three Words, Not Two! ==<br /> <br /> * Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> * Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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<br /> <br /> <br /> ==Collaborating to Avert the Digital Graveyard==<br /> <br /> * Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br /> * Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br /> <br /> 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. <br /> <br /> 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.<br /> <br /> ==Docker? VMs? EC2? Yes! With Packer.io==<br /> <br /> * Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br /> <br /> 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!<br /> <br /> == Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br /> <br /> * [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)<br /> <br /> 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.<br /> <br /> 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 &quot;nearest branch to my current location&quot; functionality to this app.<br /> <br /> Despite the &quot;development phase&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.<br /> <br /> This talk will explore the following questions:<br /> <br /> * 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.<br /> <br /> * 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.)<br /> <br /> * 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.<br /> <br /> * 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.”<br /> <br /> * 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.<br /> <br /> ==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br /> <br /> * Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br /> * Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br /> <br /> We have to &quot;turn projects into programs&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?<br /> <br /> 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!<br /> <br /> == Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br /> <br /> * Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> <br /> Annotations on content resources allow users to contribute knowledge within the digital repository space. 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 and servers can be mixed and matched.<br /> <br /> 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. This component could be used with other LDP implementations, or with some additional development to ease the migration from other linked data sources into Fedora4. <br /> <br /> The presentation will focus on the benefits of the approach with respect to following international standards to ease system integration, and lessons learnt regarding the development process.</div>

Ndushay https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=41983 2014-11-07T19:11:24Z

<p>Ndushay: revise Annotations proposal</p> <hr /> <div>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/. <br /> The conference will be held at the Portland Hilton &amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> We encourage everyone to propose a talk.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br /> * Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br /> * Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br /> * Technical issues - Big issues in library technology that should be addressed or better understood<br /> * 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.<br /> <br /> 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.<br /> <br /> '''Proposals for Prepared Talks:'''<br /> <br /> 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.<br /> Provide a title and brief (500 words or fewer) description of your proposed talk.<br /> 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.<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Talk Title: ==<br /> <br /> * Speaker's name, email address, and (optional) affiliation<br /> * Second speaker's name, email address, and affiliation, if second speaker<br /> <br /> Abstract of no more than 500 words.<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Talk Proposals'''<br /> == Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br /> <br /> * [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]<br /> * [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br /> <br /> 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!<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Both games will be demoed.<br /> <br /> We have never presented at Code4lib.<br /> <br /> == Do the Semantic FRBRoo ==<br /> * Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br /> <br /> [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?<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> == Our $50,000 Problem: Why Library School? ==<br /> * Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br /> <br /> 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.]<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> * Rachel Wittmann, rwittma@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> In this talk, we will discuss:<br /> * Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br /> * The stumbling blocks experienced in that process and how they were resolved.<br /> * 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. <br /> * A brief overview of the export and import functions and also current workflow practices within Providence.<br /> * Future plans &amp; the role of CollectiveAccess at Clemson University Libraries<br /> <br /> == Getting ContentDM and Wordpress to Play Together ==<br /> * [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br /> <br /> ==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br /> <br /> * [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br /> <br /> 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 &quot;topics&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.<br /> <br /> For more info check out http://www.docrefinery.org.<br /> <br /> ==Drupal 8 — Evolution &amp; Revolution==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br /> <br /> ==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br /> <br /> * [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br /> <br /> 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].<br /> <br /> ==The Impossible Search: Pulling data from multiple unknown sources==<br /> <br /> * Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br /> <br /> 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.<br /> <br /> ==What! You're Not Using Docker?==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> 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.<br /> <br /> *[1]https://www.docker.com/<br /> <br /> == Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br /> <br /> * Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br /> <br /> 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.<br /> <br /> == Categorizing Records with Random Forests ==<br /> <br /> * Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br /> 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. <br /> <br /> == Data Science in Libraries ==<br /> <br /> * Devon Smith, smithde@oclc.org, OCLC<br /> <br /> 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.<br /> <br /> == PDF metadata extraction for academic literature == <br /> <br /> * Kevin Savage, kevin.savage at mendeley.com, Mendeley<br /> * Joyce Stack, joyce.stack at mendeley.com, Mendeley<br /> <br /> Mendeley recently added a, &quot;document from file,&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.<br /> <br /> == Giving Users What They Want: Record Grouping in VuFind ==<br /> <br /> * Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br /> <br /> 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.<br /> <br /> == Topic Space: a mobile augmented reality recommendation app ==<br /> <br /> * Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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].<br /> <br /> == Leveling Up Your Git Workflow ==<br /> <br /> * Megan Kudzia, moneill@albion.edu, Albion College Library<br /> * Kate Sears, eks11@albion.edu, Albion College Library<br /> <br /> 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).<br /> <br /> == Drone Loaning Program: Because Laptops are so last century ==<br /> <br /> * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br /> * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br /> <br /> 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 &quot;Is the drone available?&quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br /> <br /> == Got Git? Getting More Out of Your GitHub Repositories ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br /> <br /> 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!<br /> <br /> * [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br /> * [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br /> * [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br /> * [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br /> * Gists for code sharing<br /> * Private Repositories and Organizational Groups<br /> * Pull Request Conversation Tracking<br /> * Customized Issue management<br /> <br /> == Quick Wins for Every Department in the Library - File Analyzer! ==<br /> <br /> * Terry Brady, twb27@georgetown.edu, Georgetown University Library<br /> <br /> The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating COUNTER compliant reports for the Electronic Resources department<br /> * Generating ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br /> <br /> ==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br /> <br /> * [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br /> <br /> 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. <br /> <br /> == Building Your Own Federated Search ==<br /> <br /> * Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br /> <br /> 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.<br /> <br /> 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. <br /> <br /> == Indexing Linked Data with LDPath ==<br /> <br /> * Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> [1] http://marmotta.apache.org/ldpath/language.html<br /> <br /> == Show Me the Money: Integrating an LMS with Payment Providers ==<br /> <br /> * Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br /> <br /> 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.<br /> <br /> == Shibboleth Federated Authentication for Library Applications: ==<br /> <br /> * Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br /> * Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br /> <br /> 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.<br /> <br /> ==Scientific Data: A Needs Assessment Journey==<br /> <br /> *[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br /> <br /> 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. <br /> <br /> 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. <br /> <br /> 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;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. <br /> <br /> == Feminist Human Computer Interaction (HCI) in Library Software ==<br /> <br /> * Bess Sadler, bess@stanford.edu, Stanford University Libraries<br /> <br /> 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. <br /> <br /> [1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br /> <br /> [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<br /> <br /> == Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br /> <br /> * Audrey Altman, audrey at dp.la, Digital Public Library of America<br /> * Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br /> * Mark Breedlove, mb at dp.la, Digital Public Library of America<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> == OS or GTFO: Program or Perish ==<br /> *Tessa Fallon, tessa.fallon@gmail.com<br /> <br /> Description TBD<br /> <br /> == Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br /> * Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br /> 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.<br /> <br /> == REPOX: Metadata Blender ==<br /> <br /> * John Mignault, jmignault@metro.org, Empire State Digital Network<br /> <br /> 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.<br /> <br /> == Beyond Open Source ==<br /> <br /> * Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br /> * Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br /> <br /> 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?<br /> <br /> 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.<br /> <br /> [[Category:Code4Lib2015]] <br /> [[Category:Talk Proposals]]<br /> <br /> == Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br /> <br /> * Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br /> * Max King, mking9@iit.edu, Illinois Institute of Technology<br /> <br /> 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.<br /> 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.<br /> 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.<br /> <br /> == Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br /> <br /> * Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br /> <br /> * Jefferson Bailey, jefferson@archive.org, Internet Archive<br /> * Vinay Goel, vinay@archive.org, Internet Archive<br /> <br /> 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.<br /> <br /> == Awesome Pi, LOL! ==<br /> <br /> * Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br /> * Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br /> <br /> 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.<br /> <br /> == You Gotta Keep 'em Separated: The Case for &quot;Bento Box&quot; Discovery Interfaces ==<br /> <br /> * Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br /> <br /> I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br /> <br /> 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.<br /> <br /> Now, the question is, for your &quot;everything&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?<br /> <br /> At UNT, we've been holding off on implementing an &quot;everything&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.<br /> <br /> 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 &quot;everything&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.<br /> <br /> 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 &quot;bento box&quot; discovery bandwagon and why I think &quot;bento box&quot; is at this point the path that least sells our souls.<br /> <br /> == Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br /> <br /> * Ashley Blewer!, ashley.blewer@gmail.com<br /> <br /> 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?<br /> <br /> == Level Up Your Coding with Code Club (yes, you can talk about it) ==<br /> <br /> * Coral Sheldon-Hess, coral@sheldon-hess.org<br /> <br /> 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.<br /> <br /> But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br /> <br /> 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! <br /> <br /> == The Growth of a Programmer ==<br /> <br /> * [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br /> <br /> 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.<br /> <br /> == Developing a Fedora 4.0 Content Model for Disk Images ==<br /> <br /> * Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br /> * Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br /> <br /> 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.<br /> <br /> == Data acquisition and publishing tools in R ==<br /> <br /> * Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br /> <br /> 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).<br /> <br /> == SPLUNK: Log File Analysis ==<br /> <br /> * Jim LeFager, jlefager@depaul.edu, DePaul University Library<br /> 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. <br /> <br /> == Your code does not exist in a vacuum ==<br /> * Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br /> <br /> “If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> == The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br /> <br /> * Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br /> * Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br /> <br /> 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. <br /> <br /> 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.<br /> <br /> http://chicagocollectionsconsortium.org<br /> <br /> == Programmers are not projects: lessons learned from managing humans ==<br /> <br /> * Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br /> <br /> 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.<br /> <br /> == Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br /> <br /> * Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br /> <br /> 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? <br /> <br /> 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.<br /> <br /> == A Semantic Makeover for CMS Data ==<br /> <br /> * Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br /> <br /> 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.<br /> <br /> == Taking User Experience (UX) to new heights ==<br /> <br /> * Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br /> <br /> User Experience, or &quot;UX&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:<br /> <br /> - 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.<br /> <br /> - Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &quot;heat maps&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.<br /> <br /> - Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br /> <br /> 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.<br /> <br /> ==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br /> <br /> *Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br /> *Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br /> *May Yan, Ryerson University, may.yan@ryerson.ca<br /> <br /> 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. <br /> <br /> 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: <br /> “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.” <br /> <br /> 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.<br /> <br /> ==Making your digital objects embeddable around the web==<br /> <br /> * Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==So you want to make your geospatial data discoverable==<br /> <br /> * Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br /> <br /> 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.<br /> <br /> == Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br /> <br /> * Adam Wead, awead@psu.edu, Penn State University<br /> <br /> Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br /> Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br /> wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br /> Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br /> tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br /> working solution that exhibited all the hallmarks of good testing and software design.<br /> <br /> This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br /> You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br /> problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br /> viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br /> development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br /> to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br /> <br /> <br /> == Designing and Leading a Kick A** Tech Team ==<br /> <br /> * Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br /> <br /> 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.<br /> <br /> <br /> ==American (Archives) Horror Story: LTO Failure and Data Loss ==<br /> <br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> <br /> 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!<br /> <br /> == PBCore in Action: Three Words, Not Two! ==<br /> <br /> * Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br /> * Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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<br /> <br /> <br /> ==Collaborating to Avert the Digital Graveyard==<br /> <br /> * Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br /> * Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br /> <br /> 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. <br /> <br /> 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.<br /> <br /> ==Docker? VMs? EC2? Yes! With Packer.io==<br /> <br /> * Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br /> <br /> 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!<br /> <br /> == Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br /> <br /> * [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)<br /> <br /> 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.<br /> <br /> 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 &quot;nearest branch to my current location&quot; functionality to this app.<br /> <br /> Despite the &quot;development phase&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.<br /> <br /> This talk will explore the following questions:<br /> <br /> * 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.<br /> <br /> * 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.)<br /> <br /> * 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.<br /> <br /> * 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.”<br /> <br /> * 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.<br /> <br /> ==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br /> <br /> * Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br /> * Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br /> * Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br /> * Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br /> <br /> We have to &quot;turn projects into programs&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?<br /> <br /> 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!<br /> <br /> == Annotations as Linked Data with Fedora4 and Triannon ==<br /> <br /> * Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br /> * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br /> <br /> Annotations on content resources allow users to contribute knowledge within the digital repository space. 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 and servers can be mixed and matched.<br /> <br /> 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. This component could be used with other LDP implementations, or with some additional development to ease the migration from other linked data sources into Fedora4. <br /> <br /> The presentation will focus on the benefits of the approach with respect to following international standards to ease system integration, and lessons learnt regarding the development process.</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ndushay&diff=39789 2013-11-08T00:17:13Z

<p>Ndushay: </p> <hr /> <div>Naomi Dushay<br /> <br /> Senior Discovery Engineer<br /> <br /> Digital Libraries Systems and Services<br /> <br /> Stanford University Libraries</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ndushay&diff=39788 2013-11-08T00:15:48Z

<p>Ndushay: Created page with &quot;Naomi Dushay Senior Discovery Engineer Digital Libraries Systems and Services Stanford University Libraries&quot;</p> <hr /> <div>Naomi Dushay<br /> <br /> Senior Discovery Engineer<br /> Digital Libraries Systems and Services<br /> Stanford University Libraries</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=33128 2013-01-23T17:28:45Z

<p>Ndushay: /* Solr 4 In Depth */</p> <hr /> <div>Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.<br /> <br /> Proposals '''now closed'''.<br /> <br /> Spaces available: 4+ Rooms<br /> <br /> Please follow the formatting guidelines:<br /> &lt;pre&gt;<br /> === Talk Title ===<br /> <br /> * Presenter/Leader, affiliation (optional), and email address (mandatory!)<br /> * Second Presenter/Leader, affiliation, email address, if applicable<br /> <br /> Description.<br /> &lt;/pre&gt;<br /> <br /> ==Full Day==<br /> <br /> ===Drupal4lib Sub-con Barcamp===<br /> <br /> * Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br /> * [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br /> <br /> This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br /> <br /> If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br /> <br /> This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.<br /> <br /> Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br /> <br /> ====I plan on attending:====<br /> <br /> =====All Day=====<br /> *Margaret Heller<br /> *Mahria Lebow, mahria at uw edu<br /> *Paula Gray-Overtoom, pgrayove at gmail.com<br /> *Dhanushka Samarakoon, dhanu80 at g mail com<br /> <br /> =====Morning=====<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * Sean Chen<br /> <br /> =====Afternoon=====<br /> * Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br /> * Christina Salazar (afternoon only)<br /> * Sarah Dooley (afternoon)<br /> * Josh Wilson, joshwilsonnc at gmail (likely afternoon only)<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Cody Hennesy, chennesy at library berkeley edu<br /> <br /> ==Half Day Morning==<br /> === Open space session ===<br /> <br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br /> <br /> If there's interest, we could start with a &quot;welcome to code4lib&quot; introductory session for newcomers.<br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jason Casden<br /> * Ryan Eby<br /> * mark matienzo<br /> * Donald Mennerich<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> <br /> === Delivery services ===<br /> * Ted Lawless, Brown University Library, tlawless at brown edu. <br /> * Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br /> <br /> Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br /> <br /> Possible topics/activities include:<br /> * group discussion of what some libraries have done in this area<br /> * comparisons of different approaches to addressing delivery <br /> * overview of tools available <br /> * sharing of strategies and experiences<br /> * time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. <br /> <br /> Resources and background information:<br /> * [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br /> * [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br /> * [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br /> * [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br /> <br /> '''I plan on attending:'''<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Ayla Stein<br /> * Curtis Thacker<br /> * Rosalyn Metz rosalynmetz at gmail com<br /> * James Van Mil - james.vanmil at gmail com<br /> * Andrew Nagy<br /> * Ranti Junus<br /> * Aaron Collier - acollier at csufresno edu<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Jacob Andresen - jacob at reindex dot dk<br /> * Erin White - erwhite at vcu edu<br /> * Zeno Tajoli tajoli at cilea it<br /> <br /> === Intro to Blacklight CANCELLED ===<br /> <br /> PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.<br /> <br /> === RailsBridge Intro to Ruby on Rails ===<br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> * Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br /> * Ross Singer, Talis, rossfsinger@gmail.com<br /> * Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> * James Stuart<br /> * Anyone else want to come and help folks? Contact Jason.<br /> <br /> RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. <br /> <br /> * Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br /> <br /> There is some pre-preconference preparation needed so that we can effectively use our time.<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name below<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] <br /> <br /> '''I plan on attending:'''<br /> # First and last name and email address<br /> # John MacGillivray<br /> # Jon Stroop - jstroop at princeton<br /> # Christina Salazar - christina{dot}salazar{at}csuci{dot}edu<br /> # Karen Coombs - coombsk{at}oclc{dot}org<br /> # Becky Yoose - b dot yoose at google overlord<br /> # Jeremy Morse - jgmorse at umich<br /> # Julia Bauder - julia{dot}bauder{at}gmail{dot}com <br /> # Chung Kang<br /> # Karen Miller - k-miller3{at}northwestern{dot}edu<br /> # Betsy Coles - bcoles{at}caltech{dot}edu<br /> # Jay Luker - jay{dot}luker{at}gmail{dot}com<br /> # Santi Thompson<br /> # Sarah Dooley - sarah{at}nclive{dot}org<br /> # Brandon Dudley<br /> # Ken Irwin<br /> # Dennis Ogg - ogg{at}ucar{dot}edu<br /> # Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> # Steven Villereal – villereal{at}gmail{dot}com<br /> # Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com<br /> # Josh Wilson - joshwilsonnc at gmail<br /> # Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail<br /> # Ian Chan<br /> # Heidi Frank - hf36{at}nyu{dot}edu<br /> # Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> # Bill McMillin - wmcmilli{at}pratt {dot}edu<br /> # David Lacy - david dot lacy at villanova dot edu<br /> # Courtney Greene - crgreene at indiana dot edu<br /> # Laney McGlohon - lmcglohon@getty.edu<br /> # Nancy Enneking - nenneking@getty.edu<br /> # Jason Raitz - jcraitz at ncsu dot edu<br /> # Nick Cappadona<br /> # Steven Marsden - steven.marsden@ryerson.ca<br /> # Linda Ballinger - ballingerl at newberry dot org<br /> # Brendan Quinn - brendan-quinn at northwestern dot edu<br /> # Michael Levy - mlevy {at}ushmm {dot}org<br /> # Michael North (m-north at northwestern dot edu)<br /> # Shawn Averkamp - shawnaverkamp{at}gmail{dot}com<br /> # Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> # Cody Hennesy - chennesy at library dot berkeley dot edu<br /> # Devin Higgins - higgi135 at msu dot edu<br /> # Emily Zervas - emily{dot}zervas{at}gmail{dot}com<br /> # Rob Dumas - rdumas {at} chipublib {dot} org<br /> # Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> # William Hicks - William{dot}hicks{at}unt{dot}edu<br /> # Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> # David Anderson - david dot anderson3 at nih dot gov<br /> # David Bucknum - dabu at loc dot gov<br /> # Dave Menninger - dave.menninger at gmail dot com<br /> # Chris Day - cday2 at saic dot edu<br /> # Corey Harper - corey dot harper at nyu dot edu<br /> # Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca<br /> # Harish Nayak - hnayak at library dot rochester dot edu<br /> # David Cliff dgcliff@iu.edu<br /> # Cody Hanson codyhanson@umn.edu<br /> # Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name above<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]<br /> <br /> ===Intro to NoSQL Databases===<br /> * Joshua Gomez, George Washington University, jngomez at gwu edu<br /> <br /> Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &quot;Big Data&quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br /> <br /> '''I plan on attending:'''<br /> * Esha Datta<br /> * Trevor Thornton<br /> * Michael Doran<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Kevin Clarke<br /> * Andreas Orphanides<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Harrison Dekker<br /> * Eric James eric dot james at yale dot edu<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Scott Hanrath<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Karen Coyle - kcoyle at kcoyle.net<br /> * Charles Draper<br /> * David Uspal<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Declan Fleming - declan at declan dot net<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * May Chan - msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * Eben English - eenglish [at] bpl dot org<br /> * Marisa Strong - marisa dot strong at ucop dot edu<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Julien Gibert, gibert at abes dot fr<br /> * Lisa Gonzalez, lgonzalez@ctu.edu<br /> * Charles Ledvina, charles@indexdata.com<br /> * Jim LeFager, jlefager@depaul.edu<br /> * Debbie Maron, dmaron@purdue.edu<br /> * Carolina Garcia - cg116 nyu<br /> * Tracy Seneca- tjseneca@uic.edu<br /> * William Denton - wtd@pobox.com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Gary Maixner maixner2 at uiuc dot edu<br /> <br /> ==Half Day Afternoon==<br /> === Data Visualization Hackfest ===<br /> * Chris Beer, cabeer at stanford.edu<br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> * Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &quot;Where Librarians Go To Hack&quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br /> - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br /> - we'll separate into groups and hack on stuff.<br /> - at the end of the day, we'll present our progress.<br /> <br /> Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esha Datta<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Karen Coombs - coombsk{at}oclc{dot}org<br /> * Julia Bauder - julia{dot}bauder{at}gmail{dot}com<br /> * Jason Stirnaman (jstirnaman at kumc.edu)<br /> * Joshua Gomez<br /> * Ayla Stein<br /> * Harrison Dekker<br /> * Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> * Scott Hanrath<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * James Van Mil - james.vanmil at gmail com<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Karen coyle - kcoyle at kcoyle.net<br /> * David Lacy - david dot lacy at villanova dot edu<br /> * mark matienzo<br /> * David Uspal<br /> * Emily Lynema - ejlynema at ncsu dot edu<br /> * Sean Chen<br /> * Donald Mennerich<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Declan Fleming - declan at declan dot net<br /> * Chick Markley -- chick at qrhino dot com<br /> * Rosalyn Metz -- rosalynmetz at gmail com<br /> * Devin Higgins - higgi135 at msu dot edu<br /> * Emily Zervas emily{dot}zervas{at}gmail{dot}com<br /> * May Chan -- msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Dave Menninger dave.menninger at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Rikke Willer - riwi at dtic dot dtu dot dk<br /> * Michael Poltorak NIelsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Julien Gibert, gibert at abes dot fr<br /> * Christie Peterson - cpeterson at jhu dot edu<br /> * Jim LeFager - jlefager@depaul.edu<br /> * Harish Nayak - hnayak at library dot rochester dot edu<br /> * William Denton - wtd@pobox.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> * Naomi Dushay - ndushay at stanford dot edu<br /> <br /> === Intro to Hydra ===<br /> * Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br /> * Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> <br /> Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br /> <br /> '''I plan on attending:'''<br /> * Jeremy Prevost<br /> * Dennis Ogg - ogg{at}ucar{dot}edu<br /> * Terry Brady<br /> * Betsy Coles - bcoles{at}caltech{dot}edu<br /> * Brendan Quinn - brendan-quinn at northwestern dot edu<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Steven Villereal – villereal{at}gmail{dot}com<br /> * Ryan Eby<br /> * Dean Farrell<br /> * Ian Chan<br /> * Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> * Carl Jones<br /> * Laney McGlohon - lmcglohon@getty.edu<br /> * Nancy Enneking - nenneking@getty.edu<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk<br /> * Corey Harper - corey dot harper at nyu dot edu<br /> * Gary Maixner - maixner2 at uiuc dot edu<br /> <br /> === Intro to Blacklight ===<br /> * Bess Sadler, Stanford University Library (bess at stanford.edu)<br /> * Jason Ronallo, NC State (jronallo at gmail.com)<br /> * Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br /> <br /> Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;A around local issues people might encounter. <br /> <br /> Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br /> <br /> '''I plan on attending:'''<br /> * John MacGillivray<br /> * Jon Stroop<br /> * Jeremy Morse - jgmorse at umich<br /> * Karen Miller - k-miller3{at}northwestern{dot}edu<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Chung Kang<br /> * Santi Thompson<br /> * Brandon Dudley<br /> * Ken Irwin<br /> * Hillel Arnold<br /> * Heidi Frank - hf36{at}nyu{dot}com<br /> * Chris Sharp - csharp{at}georgialibraries{dot}org<br /> * Bill McMillin - wmcmilli{at} pratt{dot} edu<br /> * Jason Raitz - jcraitz at ncsu dot edu<br /> * Linda Ballinger - ballingerl at newberry dot org<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Courtney Greene - crgreene at indiana dot edu<br /> * Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> * William Hicks - William{dot}hicks{at}unt{dot}edu<br /> * Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> * David Anderson - david dot anderson3 at nih dot gov<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * David Bucknum - dabu at loc dot gov<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * Chris Day - cday2 at saic dot edu<br /> * Carolina Garcia - cg116 nyu<br /> * David Cliff dgcliff@iu.edu<br /> * Cody Hanson codyhanson@umn.edu<br /> * Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> === DPLA Intro/Hacking ===<br /> <br /> * Presenter(s)/Leader(s): TBD<br /> * Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br /> <br /> This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Justin Clark, Berkman Center for Internet and Society<br /> * Anita Patel, Berkman Center for Internet and Society<br /> <br /> === Fail4lib ===<br /> * Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br /> * Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br /> <br /> The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&quot;The Pivot&quot;), and failing more cheaply.<br /> <br /> Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br /> <br /> # Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br /> # Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br /> #* Technical failure<br /> #* Failure to effectively address a real user need<br /> #* Overinvestment<br /> #* Outreach/Promotion failure<br /> #* Design/UX failure<br /> #* Project team communication failure<br /> #* Missed opportunities (risk-averse failure)<br /> #* Successes gleaned from failures<br /> # A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br /> # A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br /> <br /> I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br /> <br /> '''I plan on attending:'''<br /> * Becky Yoose<br /> * Lisa Rabey<br /> * Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Erin White, erwhite at vcu edu<br /> <br /> === Solr 4 In Depth ===<br /> * Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br /> <br /> The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jon Stroop<br /> * Adam Constabars<br /> * Kevin Clarke<br /> * Jacob Andresen (jacob at reindex dot dk)<br /> * Ted Lawless (tlawless at brown dot edu)<br /> * Jay Luker<br /> * Tom Burton-West<br /> * Curtis Thacker<br /> * Eric James eric dot james at yale dot edu<br /> * Bess Sadler (bess at stanford dot edu)<br /> * Michael North<br /> * Charles Draper<br /> * Nick Cappadona<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Kalee Sprague - kalee dot sprague at yale dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * Erik Hetzner<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Eben English - eenglish at bpl dot org<br /> * Raman Chandrasekar <br /> * Jason Ronallo - jnronall@ncsu.edu<br /> * Eric Larson - elarson@library.wisc.edu<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * Steven Marsden - steven.marsden@ryerson.ca<br /> * Zeno Tajoli - tajoli at cilea it<br /> * Charles Ledvina - charles att indexdata dott com<br /> * Tracy Seneca - tjseneca@uic.edu<br /> * Tod Olson - tod at uchicago dot edu<br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=33127 2013-01-23T17:28:00Z

<p>Ndushay: /* Data Visualization Hackfest */</p> <hr /> <div>Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.<br /> <br /> Proposals '''now closed'''.<br /> <br /> Spaces available: 4+ Rooms<br /> <br /> Please follow the formatting guidelines:<br /> &lt;pre&gt;<br /> === Talk Title ===<br /> <br /> * Presenter/Leader, affiliation (optional), and email address (mandatory!)<br /> * Second Presenter/Leader, affiliation, email address, if applicable<br /> <br /> Description.<br /> &lt;/pre&gt;<br /> <br /> ==Full Day==<br /> <br /> ===Drupal4lib Sub-con Barcamp===<br /> <br /> * Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br /> * [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br /> <br /> This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br /> <br /> If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br /> <br /> This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.<br /> <br /> Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br /> <br /> ====I plan on attending:====<br /> <br /> =====All Day=====<br /> *Margaret Heller<br /> *Mahria Lebow, mahria at uw edu<br /> *Paula Gray-Overtoom, pgrayove at gmail.com<br /> *Dhanushka Samarakoon, dhanu80 at g mail com<br /> <br /> =====Morning=====<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * Sean Chen<br /> <br /> =====Afternoon=====<br /> * Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br /> * Christina Salazar (afternoon only)<br /> * Sarah Dooley (afternoon)<br /> * Josh Wilson, joshwilsonnc at gmail (likely afternoon only)<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Cody Hennesy, chennesy at library berkeley edu<br /> <br /> ==Half Day Morning==<br /> === Open space session ===<br /> <br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br /> <br /> If there's interest, we could start with a &quot;welcome to code4lib&quot; introductory session for newcomers.<br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jason Casden<br /> * Ryan Eby<br /> * mark matienzo<br /> * Donald Mennerich<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> <br /> === Delivery services ===<br /> * Ted Lawless, Brown University Library, tlawless at brown edu. <br /> * Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br /> <br /> Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br /> <br /> Possible topics/activities include:<br /> * group discussion of what some libraries have done in this area<br /> * comparisons of different approaches to addressing delivery <br /> * overview of tools available <br /> * sharing of strategies and experiences<br /> * time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. <br /> <br /> Resources and background information:<br /> * [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br /> * [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br /> * [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br /> * [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br /> <br /> '''I plan on attending:'''<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Ayla Stein<br /> * Curtis Thacker<br /> * Rosalyn Metz rosalynmetz at gmail com<br /> * James Van Mil - james.vanmil at gmail com<br /> * Andrew Nagy<br /> * Ranti Junus<br /> * Aaron Collier - acollier at csufresno edu<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Jacob Andresen - jacob at reindex dot dk<br /> * Erin White - erwhite at vcu edu<br /> * Zeno Tajoli tajoli at cilea it<br /> <br /> === Intro to Blacklight CANCELLED ===<br /> <br /> PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.<br /> <br /> === RailsBridge Intro to Ruby on Rails ===<br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> * Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br /> * Ross Singer, Talis, rossfsinger@gmail.com<br /> * Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> * James Stuart<br /> * Anyone else want to come and help folks? Contact Jason.<br /> <br /> RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. <br /> <br /> * Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br /> <br /> There is some pre-preconference preparation needed so that we can effectively use our time.<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name below<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] <br /> <br /> '''I plan on attending:'''<br /> # First and last name and email address<br /> # John MacGillivray<br /> # Jon Stroop - jstroop at princeton<br /> # Christina Salazar - christina{dot}salazar{at}csuci{dot}edu<br /> # Karen Coombs - coombsk{at}oclc{dot}org<br /> # Becky Yoose - b dot yoose at google overlord<br /> # Jeremy Morse - jgmorse at umich<br /> # Julia Bauder - julia{dot}bauder{at}gmail{dot}com <br /> # Chung Kang<br /> # Karen Miller - k-miller3{at}northwestern{dot}edu<br /> # Betsy Coles - bcoles{at}caltech{dot}edu<br /> # Jay Luker - jay{dot}luker{at}gmail{dot}com<br /> # Santi Thompson<br /> # Sarah Dooley - sarah{at}nclive{dot}org<br /> # Brandon Dudley<br /> # Ken Irwin<br /> # Dennis Ogg - ogg{at}ucar{dot}edu<br /> # Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> # Steven Villereal – villereal{at}gmail{dot}com<br /> # Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com<br /> # Josh Wilson - joshwilsonnc at gmail<br /> # Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail<br /> # Ian Chan<br /> # Heidi Frank - hf36{at}nyu{dot}edu<br /> # Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> # Bill McMillin - wmcmilli{at}pratt {dot}edu<br /> # David Lacy - david dot lacy at villanova dot edu<br /> # Courtney Greene - crgreene at indiana dot edu<br /> # Laney McGlohon - lmcglohon@getty.edu<br /> # Nancy Enneking - nenneking@getty.edu<br /> # Jason Raitz - jcraitz at ncsu dot edu<br /> # Nick Cappadona<br /> # Steven Marsden - steven.marsden@ryerson.ca<br /> # Linda Ballinger - ballingerl at newberry dot org<br /> # Brendan Quinn - brendan-quinn at northwestern dot edu<br /> # Michael Levy - mlevy {at}ushmm {dot}org<br /> # Michael North (m-north at northwestern dot edu)<br /> # Shawn Averkamp - shawnaverkamp{at}gmail{dot}com<br /> # Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> # Cody Hennesy - chennesy at library dot berkeley dot edu<br /> # Devin Higgins - higgi135 at msu dot edu<br /> # Emily Zervas - emily{dot}zervas{at}gmail{dot}com<br /> # Rob Dumas - rdumas {at} chipublib {dot} org<br /> # Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> # William Hicks - William{dot}hicks{at}unt{dot}edu<br /> # Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> # David Anderson - david dot anderson3 at nih dot gov<br /> # David Bucknum - dabu at loc dot gov<br /> # Dave Menninger - dave.menninger at gmail dot com<br /> # Chris Day - cday2 at saic dot edu<br /> # Corey Harper - corey dot harper at nyu dot edu<br /> # Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca<br /> # Harish Nayak - hnayak at library dot rochester dot edu<br /> # David Cliff dgcliff@iu.edu<br /> # Cody Hanson codyhanson@umn.edu<br /> # Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name above<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]<br /> <br /> ===Intro to NoSQL Databases===<br /> * Joshua Gomez, George Washington University, jngomez at gwu edu<br /> <br /> Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &quot;Big Data&quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br /> <br /> '''I plan on attending:'''<br /> * Esha Datta<br /> * Trevor Thornton<br /> * Michael Doran<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Kevin Clarke<br /> * Andreas Orphanides<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Harrison Dekker<br /> * Eric James eric dot james at yale dot edu<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Scott Hanrath<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Karen Coyle - kcoyle at kcoyle.net<br /> * Charles Draper<br /> * David Uspal<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Declan Fleming - declan at declan dot net<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * May Chan - msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * Eben English - eenglish [at] bpl dot org<br /> * Marisa Strong - marisa dot strong at ucop dot edu<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Julien Gibert, gibert at abes dot fr<br /> * Lisa Gonzalez, lgonzalez@ctu.edu<br /> * Charles Ledvina, charles@indexdata.com<br /> * Jim LeFager, jlefager@depaul.edu<br /> * Debbie Maron, dmaron@purdue.edu<br /> * Carolina Garcia - cg116 nyu<br /> * Tracy Seneca- tjseneca@uic.edu<br /> * William Denton - wtd@pobox.com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Gary Maixner maixner2 at uiuc dot edu<br /> <br /> ==Half Day Afternoon==<br /> === Data Visualization Hackfest ===<br /> * Chris Beer, cabeer at stanford.edu<br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> * Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &quot;Where Librarians Go To Hack&quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br /> - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br /> - we'll separate into groups and hack on stuff.<br /> - at the end of the day, we'll present our progress.<br /> <br /> Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esha Datta<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Karen Coombs - coombsk{at}oclc{dot}org<br /> * Julia Bauder - julia{dot}bauder{at}gmail{dot}com<br /> * Jason Stirnaman (jstirnaman at kumc.edu)<br /> * Joshua Gomez<br /> * Ayla Stein<br /> * Harrison Dekker<br /> * Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> * Scott Hanrath<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * James Van Mil - james.vanmil at gmail com<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Karen coyle - kcoyle at kcoyle.net<br /> * David Lacy - david dot lacy at villanova dot edu<br /> * mark matienzo<br /> * David Uspal<br /> * Emily Lynema - ejlynema at ncsu dot edu<br /> * Sean Chen<br /> * Donald Mennerich<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Declan Fleming - declan at declan dot net<br /> * Chick Markley -- chick at qrhino dot com<br /> * Rosalyn Metz -- rosalynmetz at gmail com<br /> * Devin Higgins - higgi135 at msu dot edu<br /> * Emily Zervas emily{dot}zervas{at}gmail{dot}com<br /> * May Chan -- msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Dave Menninger dave.menninger at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Rikke Willer - riwi at dtic dot dtu dot dk<br /> * Michael Poltorak NIelsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Julien Gibert, gibert at abes dot fr<br /> * Christie Peterson - cpeterson at jhu dot edu<br /> * Jim LeFager - jlefager@depaul.edu<br /> * Harish Nayak - hnayak at library dot rochester dot edu<br /> * William Denton - wtd@pobox.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> * Naomi Dushay - ndushay at stanford dot edu<br /> <br /> === Intro to Hydra ===<br /> * Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br /> * Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> <br /> Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br /> <br /> '''I plan on attending:'''<br /> * Jeremy Prevost<br /> * Dennis Ogg - ogg{at}ucar{dot}edu<br /> * Terry Brady<br /> * Betsy Coles - bcoles{at}caltech{dot}edu<br /> * Brendan Quinn - brendan-quinn at northwestern dot edu<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Steven Villereal – villereal{at}gmail{dot}com<br /> * Ryan Eby<br /> * Dean Farrell<br /> * Ian Chan<br /> * Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> * Carl Jones<br /> * Laney McGlohon - lmcglohon@getty.edu<br /> * Nancy Enneking - nenneking@getty.edu<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk<br /> * Corey Harper - corey dot harper at nyu dot edu<br /> * Gary Maixner - maixner2 at uiuc dot edu<br /> <br /> === Intro to Blacklight ===<br /> * Bess Sadler, Stanford University Library (bess at stanford.edu)<br /> * Jason Ronallo, NC State (jronallo at gmail.com)<br /> * Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br /> <br /> Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;A around local issues people might encounter. <br /> <br /> Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br /> <br /> '''I plan on attending:'''<br /> * John MacGillivray<br /> * Jon Stroop<br /> * Jeremy Morse - jgmorse at umich<br /> * Karen Miller - k-miller3{at}northwestern{dot}edu<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Chung Kang<br /> * Santi Thompson<br /> * Brandon Dudley<br /> * Ken Irwin<br /> * Hillel Arnold<br /> * Heidi Frank - hf36{at}nyu{dot}com<br /> * Chris Sharp - csharp{at}georgialibraries{dot}org<br /> * Bill McMillin - wmcmilli{at} pratt{dot} edu<br /> * Jason Raitz - jcraitz at ncsu dot edu<br /> * Linda Ballinger - ballingerl at newberry dot org<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Courtney Greene - crgreene at indiana dot edu<br /> * Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> * William Hicks - William{dot}hicks{at}unt{dot}edu<br /> * Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> * David Anderson - david dot anderson3 at nih dot gov<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * David Bucknum - dabu at loc dot gov<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * Chris Day - cday2 at saic dot edu<br /> * Carolina Garcia - cg116 nyu<br /> * David Cliff dgcliff@iu.edu<br /> * Cody Hanson codyhanson@umn.edu<br /> * Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> === DPLA Intro/Hacking ===<br /> <br /> * Presenter(s)/Leader(s): TBD<br /> * Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br /> <br /> This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Justin Clark, Berkman Center for Internet and Society<br /> * Anita Patel, Berkman Center for Internet and Society<br /> <br /> === Fail4lib ===<br /> * Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br /> * Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br /> <br /> The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&quot;The Pivot&quot;), and failing more cheaply.<br /> <br /> Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br /> <br /> # Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br /> # Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br /> #* Technical failure<br /> #* Failure to effectively address a real user need<br /> #* Overinvestment<br /> #* Outreach/Promotion failure<br /> #* Design/UX failure<br /> #* Project team communication failure<br /> #* Missed opportunities (risk-averse failure)<br /> #* Successes gleaned from failures<br /> # A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br /> # A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br /> <br /> I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br /> <br /> '''I plan on attending:'''<br /> * Becky Yoose<br /> * Lisa Rabey<br /> * Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Erin White, erwhite at vcu edu<br /> <br /> === Solr 4 In Depth ===<br /> * Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br /> <br /> The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jon Stroop<br /> * Adam Constabars<br /> * Kevin Clarke<br /> * Jacob Andresen (jacob at reindex dot dk)<br /> * Ted Lawless (tlawless at brown dot edu)<br /> * Jay Luker<br /> * Tom Burton-West<br /> * Curtis Thacker<br /> * Eric James eric dot james at yale dot edu<br /> * Bess Sadler (bess at stanford dot edu)<br /> * Michael North<br /> * Charles Draper<br /> * Nick Cappadona<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Kalee Sprague - kalee dot sprague at yale dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * Erik Hetzner<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Eben English - eenglish at bpl dot org<br /> * Raman Chandrasekar <br /> * Jason Ronallo - jnronall@ncsu.edu<br /> * Eric Larson - elarson@library.wisc.edu<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * Steven Marsden - steven.marsden@ryerson.ca<br /> * Zeno Tajoli - tajoli at cilea it<br /> * Charles Ledvina - charles att indexdata dott com<br /> * Tracy Seneca - tjseneca@uic.edu<br /> * Tod Olson - tod at uchicago dot edu<br /> * Naomi Dushay - ndushay at stanford dot edu<br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=33126 2013-01-23T17:27:21Z

<p>Ndushay: /* Solr 4 In Depth */</p> <hr /> <div>Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.<br /> <br /> Proposals '''now closed'''.<br /> <br /> Spaces available: 4+ Rooms<br /> <br /> Please follow the formatting guidelines:<br /> &lt;pre&gt;<br /> === Talk Title ===<br /> <br /> * Presenter/Leader, affiliation (optional), and email address (mandatory!)<br /> * Second Presenter/Leader, affiliation, email address, if applicable<br /> <br /> Description.<br /> &lt;/pre&gt;<br /> <br /> ==Full Day==<br /> <br /> ===Drupal4lib Sub-con Barcamp===<br /> <br /> * Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br /> * [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br /> <br /> This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br /> <br /> If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br /> <br /> This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.<br /> <br /> Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br /> <br /> ====I plan on attending:====<br /> <br /> =====All Day=====<br /> *Margaret Heller<br /> *Mahria Lebow, mahria at uw edu<br /> *Paula Gray-Overtoom, pgrayove at gmail.com<br /> *Dhanushka Samarakoon, dhanu80 at g mail com<br /> <br /> =====Morning=====<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * Sean Chen<br /> <br /> =====Afternoon=====<br /> * Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br /> * Christina Salazar (afternoon only)<br /> * Sarah Dooley (afternoon)<br /> * Josh Wilson, joshwilsonnc at gmail (likely afternoon only)<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Cody Hennesy, chennesy at library berkeley edu<br /> <br /> ==Half Day Morning==<br /> === Open space session ===<br /> <br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br /> <br /> If there's interest, we could start with a &quot;welcome to code4lib&quot; introductory session for newcomers.<br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jason Casden<br /> * Ryan Eby<br /> * mark matienzo<br /> * Donald Mennerich<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> <br /> === Delivery services ===<br /> * Ted Lawless, Brown University Library, tlawless at brown edu. <br /> * Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br /> <br /> Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br /> <br /> Possible topics/activities include:<br /> * group discussion of what some libraries have done in this area<br /> * comparisons of different approaches to addressing delivery <br /> * overview of tools available <br /> * sharing of strategies and experiences<br /> * time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. <br /> <br /> Resources and background information:<br /> * [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br /> * [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br /> * [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br /> * [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br /> <br /> '''I plan on attending:'''<br /> * Ken Varnum, varnum at umich e-d-u<br /> * Ayla Stein<br /> * Curtis Thacker<br /> * Rosalyn Metz rosalynmetz at gmail com<br /> * James Van Mil - james.vanmil at gmail com<br /> * Andrew Nagy<br /> * Ranti Junus<br /> * Aaron Collier - acollier at csufresno edu<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Jacob Andresen - jacob at reindex dot dk<br /> * Erin White - erwhite at vcu edu<br /> * Zeno Tajoli tajoli at cilea it<br /> <br /> === Intro to Blacklight CANCELLED ===<br /> <br /> PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.<br /> <br /> === RailsBridge Intro to Ruby on Rails ===<br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> * Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br /> * Ross Singer, Talis, rossfsinger@gmail.com<br /> * Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> * James Stuart<br /> * Anyone else want to come and help folks? Contact Jason.<br /> <br /> RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. <br /> <br /> * Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br /> <br /> There is some pre-preconference preparation needed so that we can effectively use our time.<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name below<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] <br /> <br /> '''I plan on attending:'''<br /> # First and last name and email address<br /> # John MacGillivray<br /> # Jon Stroop - jstroop at princeton<br /> # Christina Salazar - christina{dot}salazar{at}csuci{dot}edu<br /> # Karen Coombs - coombsk{at}oclc{dot}org<br /> # Becky Yoose - b dot yoose at google overlord<br /> # Jeremy Morse - jgmorse at umich<br /> # Julia Bauder - julia{dot}bauder{at}gmail{dot}com <br /> # Chung Kang<br /> # Karen Miller - k-miller3{at}northwestern{dot}edu<br /> # Betsy Coles - bcoles{at}caltech{dot}edu<br /> # Jay Luker - jay{dot}luker{at}gmail{dot}com<br /> # Santi Thompson<br /> # Sarah Dooley - sarah{at}nclive{dot}org<br /> # Brandon Dudley<br /> # Ken Irwin<br /> # Dennis Ogg - ogg{at}ucar{dot}edu<br /> # Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> # Steven Villereal – villereal{at}gmail{dot}com<br /> # Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com<br /> # Josh Wilson - joshwilsonnc at gmail<br /> # Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail<br /> # Ian Chan<br /> # Heidi Frank - hf36{at}nyu{dot}edu<br /> # Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> # Bill McMillin - wmcmilli{at}pratt {dot}edu<br /> # David Lacy - david dot lacy at villanova dot edu<br /> # Courtney Greene - crgreene at indiana dot edu<br /> # Laney McGlohon - lmcglohon@getty.edu<br /> # Nancy Enneking - nenneking@getty.edu<br /> # Jason Raitz - jcraitz at ncsu dot edu<br /> # Nick Cappadona<br /> # Steven Marsden - steven.marsden@ryerson.ca<br /> # Linda Ballinger - ballingerl at newberry dot org<br /> # Brendan Quinn - brendan-quinn at northwestern dot edu<br /> # Michael Levy - mlevy {at}ushmm {dot}org<br /> # Michael North (m-north at northwestern dot edu)<br /> # Shawn Averkamp - shawnaverkamp{at}gmail{dot}com<br /> # Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> # Cody Hennesy - chennesy at library dot berkeley dot edu<br /> # Devin Higgins - higgi135 at msu dot edu<br /> # Emily Zervas - emily{dot}zervas{at}gmail{dot}com<br /> # Rob Dumas - rdumas {at} chipublib {dot} org<br /> # Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> # William Hicks - William{dot}hicks{at}unt{dot}edu<br /> # Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> # David Anderson - david dot anderson3 at nih dot gov<br /> # David Bucknum - dabu at loc dot gov<br /> # Dave Menninger - dave.menninger at gmail dot com<br /> # Chris Day - cday2 at saic dot edu<br /> # Corey Harper - corey dot harper at nyu dot edu<br /> # Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca<br /> # Harish Nayak - hnayak at library dot rochester dot edu<br /> # David Cliff dgcliff@iu.edu<br /> # Cody Hanson codyhanson@umn.edu<br /> # Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> '''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:<br /> # Add your name above<br /> # fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]<br /> # read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]<br /> <br /> ===Intro to NoSQL Databases===<br /> * Joshua Gomez, George Washington University, jngomez at gwu edu<br /> <br /> Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &quot;Big Data&quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br /> <br /> '''I plan on attending:'''<br /> * Esha Datta<br /> * Trevor Thornton<br /> * Michael Doran<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Kevin Clarke<br /> * Andreas Orphanides<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Harrison Dekker<br /> * Eric James eric dot james at yale dot edu<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Scott Hanrath<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Karen Coyle - kcoyle at kcoyle.net<br /> * Charles Draper<br /> * David Uspal<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Declan Fleming - declan at declan dot net<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * May Chan - msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * Eben English - eenglish [at] bpl dot org<br /> * Marisa Strong - marisa dot strong at ucop dot edu<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Michael Poltorak Nielsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Julien Gibert, gibert at abes dot fr<br /> * Lisa Gonzalez, lgonzalez@ctu.edu<br /> * Charles Ledvina, charles@indexdata.com<br /> * Jim LeFager, jlefager@depaul.edu<br /> * Debbie Maron, dmaron@purdue.edu<br /> * Carolina Garcia - cg116 nyu<br /> * Tracy Seneca- tjseneca@uic.edu<br /> * William Denton - wtd@pobox.com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Gary Maixner maixner2 at uiuc dot edu<br /> <br /> ==Half Day Afternoon==<br /> === Data Visualization Hackfest ===<br /> * Chris Beer, cabeer at stanford.edu<br /> * Dan Chudnov, dchud at gwu edu<br /> <br /> * Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &quot;Where Librarians Go To Hack&quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br /> - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br /> - we'll separate into groups and hack on stuff.<br /> - at the end of the day, we'll present our progress.<br /> <br /> Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br /> <br /> '''I plan on attending:'''<br /> * Devon Smith<br /> * Esha Datta<br /> * Ray Schwartz - schwartzr2@wpunj.edu<br /> * Karen Coombs - coombsk{at}oclc{dot}org<br /> * Julia Bauder - julia{dot}bauder{at}gmail{dot}com<br /> * Jason Stirnaman (jstirnaman at kumc.edu)<br /> * Joshua Gomez<br /> * Ayla Stein<br /> * Harrison Dekker<br /> * Ian Walls - iwalls{at}library{dot}umass{dot}edu<br /> * Scott Hanrath<br /> * [[User:Kevenj|Keven Jeffery]]<br /> * James Van Mil - james.vanmil at gmail com<br /> * Sean Crowe - sean.crowe@uc.edu<br /> * Karen coyle - kcoyle at kcoyle.net<br /> * David Lacy - david dot lacy at villanova dot edu<br /> * mark matienzo<br /> * David Uspal<br /> * Emily Lynema - ejlynema at ncsu dot edu<br /> * Sean Chen<br /> * Donald Mennerich<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Declan Fleming - declan at declan dot net<br /> * Chick Markley -- chick at qrhino dot com<br /> * Rosalyn Metz -- rosalynmetz at gmail com<br /> * Devin Higgins - higgi135 at msu dot edu<br /> * Emily Zervas emily{dot}zervas{at}gmail{dot}com<br /> * May Chan -- msuicat at gmail dot com<br /> * Kathryn Stine - kathryn dot stine at ucop dot edu<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * James Griffin - griffinj at lafayette dot edu<br /> * Dave Menninger dave.menninger at gmail dot com<br /> * [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu<br /> * Rikke Willer - riwi at dtic dot dtu dot dk<br /> * Michael Poltorak NIelsen mn at statsbiblioteket dot dk<br /> * Mads Villadsen, mv@statsbiblioteket.dk<br /> * Jørn Thøgersen, jt@statsbiblioteket.dk<br /> * Joe Atzberger, ohiocore@gmail.com<br /> * Julien Gibert, gibert at abes dot fr<br /> * Christie Peterson - cpeterson at jhu dot edu<br /> * Jim LeFager - jlefager@depaul.edu<br /> * Harish Nayak - hnayak at library dot rochester dot edu<br /> * William Denton - wtd@pobox.com<br /> * Shawn Carraway carraways at midlandstech dot edu<br /> <br /> === Intro to Hydra ===<br /> * Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br /> * Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)<br /> * Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br /> <br /> Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br /> <br /> '''I plan on attending:'''<br /> * Jeremy Prevost<br /> * Dennis Ogg - ogg{at}ucar{dot}edu<br /> * Terry Brady<br /> * Betsy Coles - bcoles{at}caltech{dot}edu<br /> * Brendan Quinn - brendan-quinn at northwestern dot edu<br /> * Shawn Kiewel - smkiewel at uga dot edu<br /> * Steven Villereal – villereal{at}gmail{dot}com<br /> * Ryan Eby<br /> * Dean Farrell<br /> * Ian Chan<br /> * Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu<br /> * Carl Jones<br /> * Laney McGlohon - lmcglohon@getty.edu<br /> * Nancy Enneking - nenneking@getty.edu<br /> * Allan Berry - allan{dot}berry{at}gmail{dot}com<br /> * Andrew Darby - agdarby at miami dot edu<br /> * Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk<br /> * Corey Harper - corey dot harper at nyu dot edu<br /> * Gary Maixner - maixner2 at uiuc dot edu<br /> <br /> === Intro to Blacklight ===<br /> * Bess Sadler, Stanford University Library (bess at stanford.edu)<br /> * Jason Ronallo, NC State (jronallo at gmail.com)<br /> * Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br /> <br /> Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;A around local issues people might encounter. <br /> <br /> Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br /> <br /> '''I plan on attending:'''<br /> * John MacGillivray<br /> * Jon Stroop<br /> * Jeremy Morse - jgmorse at umich<br /> * Karen Miller - k-miller3{at}northwestern{dot}edu<br /> * Tommy Ingulfsen - tommying{at}caltech{dot}edu<br /> * Chung Kang<br /> * Santi Thompson<br /> * Brandon Dudley<br /> * Ken Irwin<br /> * Hillel Arnold<br /> * Heidi Frank - hf36{at}nyu{dot}com<br /> * Chris Sharp - csharp{at}georgialibraries{dot}org<br /> * Bill McMillin - wmcmilli{at} pratt{dot} edu<br /> * Jason Raitz - jcraitz at ncsu dot edu<br /> * Linda Ballinger - ballingerl at newberry dot org<br /> * Tim Thompson - t.thompson5{at}miami{dot}edu<br /> * David Gonzalez - d.gonzalez26 at umiami dot edu<br /> * Courtney Greene - crgreene at indiana dot edu<br /> * Evan Boyd - eboyd /at/ ctschicago /period/ edu<br /> * William Hicks - William{dot}hicks{at}unt{dot}edu<br /> * Lauren Ajamie - lauren dot ajamie at nd dot edu<br /> * David Anderson - david dot anderson3 at nih dot gov<br /> * Michael Lindsey - mackeral at gmail dot com<br /> * David Bucknum - dabu at loc dot gov<br /> * Scott Fisher - first/last name with dot in between at ucop dot edu<br /> * Chris Day - cday2 at saic dot edu<br /> * Carolina Garcia - cg116 nyu<br /> * David Cliff dgcliff@iu.edu<br /> * Cody Hanson codyhanson@umn.edu<br /> * Laurie Lee Moses lmoses{at}colum{dot}edu<br /> <br /> === DPLA Intro/Hacking ===<br /> <br /> * Presenter(s)/Leader(s): TBD<br /> * Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br /> <br /> This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Justin Clark, Berkman Center for Internet and Society<br /> * Anita Patel, Berkman Center for Internet and Society<br /> <br /> === Fail4lib ===<br /> * Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br /> * Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br /> <br /> The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&quot;The Pivot&quot;), and failing more cheaply.<br /> <br /> Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br /> <br /> # Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br /> # Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br /> #* Technical failure<br /> #* Failure to effectively address a real user need<br /> #* Overinvestment<br /> #* Outreach/Promotion failure<br /> #* Design/UX failure<br /> #* Project team communication failure<br /> #* Missed opportunities (risk-averse failure)<br /> #* Successes gleaned from failures<br /> # A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br /> # A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br /> <br /> I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br /> <br /> '''I plan on attending:'''<br /> * Becky Yoose<br /> * Lisa Rabey<br /> * Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail<br /> * Patrick Berry, pberry@csuchico.edu<br /> * Erin White, erwhite at vcu edu<br /> <br /> === Solr 4 In Depth ===<br /> * Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br /> <br /> The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?<br /> <br /> '''I plan on attending:'''<br /> * First and last name<br /> * Erin Fahy - erin.fahy at mtholyoke edu<br /> * Esmé Cowles, escowles@ucsd.edu<br /> * Jon Stroop<br /> * Adam Constabars<br /> * Kevin Clarke<br /> * Jacob Andresen (jacob at reindex dot dk)<br /> * Ted Lawless (tlawless at brown dot edu)<br /> * Jay Luker<br /> * Tom Burton-West<br /> * Curtis Thacker<br /> * Eric James eric dot james at yale dot edu<br /> * Bess Sadler (bess at stanford dot edu)<br /> * Michael North<br /> * Charles Draper<br /> * Nick Cappadona<br /> * Stephanie Collett - stephanie dot collett at ucop dot edu<br /> * Kalee Sprague - kalee dot sprague at yale dot edu<br /> * Jeff Peterson - gpeterso at umn dot edu<br /> * Erik Hetzner<br /> * Demian Katz - demian dot katz at villanova dot edu<br /> * Eben English - eenglish at bpl dot org<br /> * Raman Chandrasekar <br /> * Jason Ronallo - jnronall@ncsu.edu<br /> * Eric Larson - elarson@library.wisc.edu<br /> * Mike Hagedon - hagedonm at u dot library dot arizona dot edu<br /> * Jesse Brown - jfbrown78 at gmail dot com<br /> * Steven Marsden - steven.marsden@ryerson.ca<br /> * Zeno Tajoli - tajoli at cilea it<br /> * Charles Ledvina - charles att indexdata dott com<br /> * Tracy Seneca - tjseneca@uic.edu<br /> * Tod Olson - tod at uchicago dot edu<br /> * Naomi Dushay - ndushay at stanford dot edu<br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_talks_proposals&diff=28843 2012-11-27T07:30:28Z

<p>Ndushay: /* Hands off! Best Practices and Top Ten Lists for Code Handoffs */</p> <hr /> <div>'''Voting is complete. See results at: http://vote.code4lib.org/election/results/24'''<br /> <br /> <br /> Deadline for talk submission '''has closed'''. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br /> * tools (some cool new software, software library or integration platform)<br /> * specs (how to get the most out of some protocols, or proposals for new ones)<br /> * challenges (one or more big problems we should collectively address)<br /> <br /> The community will vote on proposals using the criteria of:<br /> * usefulness<br /> * newness<br /> * geekiness<br /> * uniqueness<br /> * awesomeness<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> == Talk Title ==<br /> <br /> * Speaker's name, affiliation, and email address<br /> * Second speaker's name, affiliation, email address, if applicable<br /> <br /> Abstract of no more than 500 words.<br /> &lt;/pre&gt;<br /> <br /> == All Teh Metadatas Re-Revisited ==<br /> <br /> * Esme Cowles, UC San Diego Library, escowles AT ucsd DOT edu<br /> * Matt Critchlow, UC San Diego Library, mcritchlow AT ucsd DOT edu<br /> * Bradley Westbrook, UC San Diego Library, bdwestbrook AT ucsd DOT edu<br /> <br /> Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC<br /> San Diego Library Digital Asset Management system and RDF data model. You<br /> may be shocked to hear that all that metadata wasn't quite enough to<br /> handle increasingly complex digital library and research data in an<br /> elegant way. Our ad-hoc, 8-year-old data model has also been added to in<br /> inconsistent ways and our librarians and developers have not always been<br /> perfectly in sync in understanding how the data model has evolved over<br /> time.<br /> <br /> <br /> In this presentation we'll review our process of locking a team of<br /> librarians and developers in a room to figure out a new data model, from<br /> domain definition through building and testing an OWL ontology. We¹ll also<br /> cover the challenges we ran into, including the review of existing<br /> controlled vocabularies and ontologies, or lack thereof, and the decisions<br /> made to cover the gaps. Finally, we'll discuss how we engaged the digital<br /> library community for feedback and what we have to do next. We all know<br /> that Things Fall Apart, this is our attempt at Doing Better This Time.<br /> <br /> == Modernizing VuFind with Zend Framework 2 ==<br /> <br /> * Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu<br /> <br /> When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.<br /> <br /> == Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==<br /> <br /> * [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br /> <br /> Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby. <br /> Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]? <br /> It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.<br /> So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?<br /> This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.<br /> <br /> == Drupal 8 Preview — Symfony and Twig ==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.<br /> <br /> It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.<br /> <br /> Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.<br /> <br /> == Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==<br /> <br /> * Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu<br /> <br /> Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &quot;Let's digitize these together and make them one big awesome project to support public urban history&quot;? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of &quot;grand ideas crushed by technological limitations&quot; and &quot;projects on the right track&quot; to follow. <br /> <br /> == ResCarta Tools building a standard format for audio archiving, discovery and display ==<br /> <br /> * [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org<br /> <br /> The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit. <br /> <br /> Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.<br /> <br /> ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! <br /> <br /> You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old) <br /> <br /> == Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==<br /> <br /> * Michael Doran, University of Texas at Arlington, doran@uta.edu<br /> <br /> This presentation will use a seemingly simple data point, the &quot;format&quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. <br /> <br /> I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session. <br /> <br /> == Touch Kiosk 2: Piezoelectric Boogaloo ==<br /> <br /> * Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu<br /> <br /> At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.<br /> <br /> In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.<br /> <br /> I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.<br /> <br /> [1] http://journal.code4lib.org/articles/5832<br /> <br /> == Wayfinding in a Cloud: Location Service for libraries ==<br /> <br /> * Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi<br /> <br /> Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.<br /> <br /> The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.<br /> <br /> The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.<br /> <br /> == Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.<br /> * Automatically inventory a collection of documents or images to be uploaded<br /> * Generate a spreadsheet for metadata capture based on the inventory<br /> * Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested<br /> * Validate the contents of ingest folders prior to initiating the ingest to DSpace<br /> * Present users with a simple, web-based form to initiate the batch ingest process<br /> <br /> The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections. <br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == Quality Assurance Reports for DSpace Collections ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection<br /> <br /> These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.<br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==<br /> <br /> * Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca<br /> * Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca<br /> <br /> In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.<br /> <br /> See article: http://journal.code4lib.org/articles/7470<br /> <br /> == HTML5 Video Now! ==<br /> <br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> <br /> Can you use HTML5 video now? Yes.<br /> <br /> I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. We'll look at how to interact with video (and other time-based media) via JavaScript. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.<br /> <br /> My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.<br /> <br /> == Hybrid Archival Collections Using Blacklight and Hydra ==<br /> <br /> * Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org<br /> <br /> At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.<br /> <br /> Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.<br /> <br /> == Making the Web Accessible through Solid Design ==<br /> <br /> * [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp; Archives<br /> <br /> In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.<br /> <br /> While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.<br /> <br /> == Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp; Much More ==<br /> <br /> * Steven Marsden, Ryerson University Library &amp; Archives, steven dot marsden at ryerson dot ca<br /> * [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp; Archives<br /> <br /> Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. <br /> <br /> The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.<br /> <br /> The presentation will not only cover the technical aspects, but also the implementation and usability findings.<br /> <br /> == De-sucking the Library User Experience ==<br /> <br /> * Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu<br /> <br /> Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.<br /> <br /> The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.<br /> <br /> == Solr Testing Is Easy with Rspec-Solr Gem ==<br /> <br /> * Naomi Dushay, Stanford University, ndushay AT stanford DOT edu<br /> <br /> How do you know if <br /> <br /> * your idea for &quot;left anchoring&quot; searches actually works?<br /> * your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?<br /> * tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?<br /> * changes to your solrconfig file accomplish what you wanted without breaking anything else?<br /> <br /> Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:<br /> <br />  it &quot;unstemmed author name Zare should precede stemmed variants&quot; do<br />   resp = solr_response(author_search_args('Zare').merge({'fl'=&gt;'id,author_person_display', 'facet'=&gt;false}))<br />   resp.should include(&quot;author_person_display&quot; =&gt; /\bZare\W/).in_each_of_first(3).documents<br />   resp.should_not include(&quot;author_person_display&quot; =&gt; /Zaring/).in_each_of_first(20).documents<br />  end<br />   <br />  it &quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&quot; do<br />    resp = solr_resp_doc_ids_only({'q'=&gt;'Восемьсoт семьдесят один день'})<br />    resp.should include(&quot;9091779&quot;)<br />  end<br /> <br />  it &quot;q of 'String quartets Parts' and variants should be plausible &quot; do<br />    resp = solr_resp_doc_ids_only({'q'=&gt;'String quartets Parts'})<br />    resp.should have_at_least(2000).documents<br />    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'(String quartets Parts)'}))<br />    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&gt;'&quot;String quartets Parts&quot;'}))<br />  end<br /> <br /> it &quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&quot; do<br /> resp = solr_response({'q'=&gt;'三國誌', 'fl'=&gt;'id', 'facet'=&gt;false}) <br /> resp.should have_at_least(240).documents<br /> resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'三国志'})) <br /> end<br /> <br /> See<br />    http://rubydoc.info/github/sul-dlss/rspec-solr/frames<br />    https://github.com/sul-dlss/rspec-solr<br /> <br /> and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:<br />    https://github.com/sul-dlss/sw_index_tests<br /> <br /> == Northwestern's Digital Image Library ==<br /> <br /> *Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu<br /> *Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu<br /> <br /> At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL). DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:<br /> <br /> *Build custom collection of images using drag-and-drop<br /> *Re-order images within a collection using drag-and-drop<br /> *Nest collections within other collections<br /> *Create details/crops of images<br /> *Zoom, rotate images<br /> *Upload personal images<br /> *Retrieve your own uploads and details from a collection<br /> *Export a collection to a PowerPoint presentation<br /> *Create a group of users and authorize access to your images<br /> *Batch edit image metadata<br /> <br /> Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.<br /> <br /> == Two standards in a software (to say nothing of Normarc) ==<br /> <br /> *Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it<br /> <br /> With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:<br /> MARC21, Unimarc and Normarc. The main points of the presentation:<br /> <br /> *Three MARC at MySQL level<br /> *Three MARC at API level<br /> *Three MARC at display<br /> *Can I add a new format ?<br /> <br /> == Future Friendly Web Design for Libraries ==<br /> <br /> *[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu<br /> <br /> Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be &quot;redesign&quot;) - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing. <br /> <br /> So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything. <br /> <br /> Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.<br /> <br /> This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.<br /> <br /> ==BYU's discovery layer service aggregator==<br /> <br /> *Curtis Thacker, Brigham Young University, curtis.thacker AT byu DOT edu<br /> <br /> It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:<br /> <br /> *filmfinder - a tool for browsing and searching films<br /> *A custom book recommender service based on checkout data<br /> *Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.<br /> *A very geeky and powerful utility used for converting marc XML into primo compliant xml.<br /> *Embedded floormaps<br /> *A responsive web design<br /> *Bing did-you-mean<br /> *And many more.<br /> <br /> I will demo the system, review the archtecture and talk about future plans.<br /> <br /> ==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==<br /> <br /> * Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu<br /> * Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu<br /> <br /> Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:<br /> <br /> * The ingest, search, and discovery functionality of the Hydra framework<br /> * The powerful multimedia workflow management features of Opencast Matterhorn<br /> * The flexible Engage audio/video player<br /> * The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)<br /> <br /> Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.<br /> <br /> Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.<br /> <br /> == The DH Curation Guide: Building a Community Resource == <br /> <br /> *Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu <br /> *James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu <br /> <br /> Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions. <br /> <br /> Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners. <br /> <br /> This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow. <br /> <br /> == Solr Update == <br /> <br /> *Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com <br /> <br /> Solr is continually improving. Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features. It's tough for us all to keep up with the various versions and capabilities.<br /> <br /> This talk will blaze through the highlights of new features and improvements in Solr 4 (and up). Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features. We will focus on the features library coders really need to know about.<br /> <br /> == Reports for the People == <br /> <br /> *Kara Young, Keene State College, NH, kyoung1 at keene.edu<br /> *Dana Clark, Keene State College, NH, dclark5 at keene.edu<br /> <br /> Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward. In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty. Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier. Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.<br /> <br /> The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis. The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation. <br /> The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!<br /> <br /> == Network Analyses of Library Catalog Data ==<br /> <br /> * Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu<br /> * Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu <br /> <br /> Library collections are all too often like icebergs: The amount exposed on the surface is only a fraction of the actual amount of content, and we’d like to recommend relevant items from deep within the catalog to users. With the assistance of an XSEDE Allocation grant (http://xsede.org), we’ve used R to reconstitute anonymous circulation data from the University of Illinois’s library catalog into separate user transactions. The transaction data is incorporated into subject analyses that use XSEDE supercomputing resources to generate predictive network analyses and visualizations of subject areas searched by library users using Gephi (https://gephi.org/). The test data set for developing the subject analyses consisted of approximately 38,000 items from the Literatures and Languages Library that contained 110,000 headings and 130,620 transactions. We’re currently working on developing a recommender system within VuFind to display the results of these analyses.<br /> <br /> == Pitfall! Working with Legacy Born Digital Materials in Special Collections ==<br /> <br /> * Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com<br /> * Mark A. Matienzo, Yale University Library, mark AT matienzo.org<br /> <br /> Archives and special collections are being faced with a growing abundance of born digital material, as well as an abundance of many promising tools for managing them. However, one must consider the potential problems that can arise when approaching a collection containing legacy materials (from roughly the pre-internet era). Many of the tried and true, &quot;best of breed&quot; tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of &quot;word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer&quot; (Kirschenbaum, &quot;Breaking &lt;code&gt;badflag&lt;/code&gt;&quot;).<br /> <br /> Our presentation will focus on some of the strange problems encountered and creative solutions devised by two digital archivists in the course of preserving, processing, and providing access to collections at their institutions. We'll be placing particular particular emphasis of the pitfalls and crocodiles we've learned to swing over safely, while collecting treasure in the process. We'll address working with CP/M disks in collections of authors' papers, reconstructing a multipart hard drive backup spread across floppy disks, and more. <br /> <br /> == Project &lt;s&gt;foobar&lt;/s&gt; FUBAR ==<br /> <br /> * Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu<br /> <br /> Be it mandated from Those In A Higher Pay Grade Than You or self-inflicted, many of us deal with managing major library-related technology projects [1]. It’s common nowadays to manage multiple technology projects, and generally external and internal issues can be planned for to minimize project timeline shifts and quality of deliverables. Life, however, has other plans for you, and all your major library technology infrastructure projects pile on top of each other at the same time. How do you and your staff survive a train wreck of technology projects and produce deliverables to project stakeholders without having to go into the library IT version of the United States Federal Witness Protection Program?<br /> <br /> This session covers my experience with the collision of three major library technology projects - including a new institutional repository and an integrated library system migration - and how we dealt with external and internal factors, implemented damage control, and overall lessening the damage from the epic crash. You might laugh, you might cry, you will probably have flashbacks from previous projects, but you will come out of this session with a set of tools to use when you’re dealing with managing mission-critical projects.<br /> <br /> [1] Past code4lib talks have covered specific project management strategies, such as Agile, for application development. I will be focusing on and discussing general project management practices in relation to various library technology projects, many of which these strategies include in their own structures.<br /> <br /> == Implementing RFID in an Academic Library == <br /> <br /> * Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu<br /> <br /> Coastal Carolina University’s Kimbel Library recently implemented RFID to increase security, provide better inventory control over library materials and enable do-it-yourself patron services such as self checkout. <br /> <br /> I’ll give a quick overview of RFID and the components involved and then will talk about how our library utilized the technology. It takes a lot of research, time, money and not too little resourcefulness to make your library RFID-ready. I’ll show how we developed our project timeline, how we assessed and evaluated vendors and how we navigated the bid process. I’ll also talk about hardware and software installation, configuration and troubleshooting and will discuss our book and media collection encoding process. <br /> <br /> We encountered myriad issues with our vendor, the hardware and the software. Would we do it all over again? Should your library consider RFID? Caveats abound...<br /> <br /> == Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==<br /> <br /> * Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu<br /> <br /> The Kimbel Library Intranet is coded in Drupal 7, and was created to increase staff communication and store documentation. This presentation will contain an overview of our intranet project, including the modules we used, implementation issues, and possible directions in future development phases. I won’t forget to talk about the slew of tasty development issues we faced, including dealing with our university IT department, user buy-in, site navigation, user roles, project management, training and mobile modules (or the lack thereof). And some other fun (mostly) true anecdotes will surely be shared. <br /> <br /> The main functions of Phase I of this project were to increase communication across departments and committees, facilitate project management and revise the library's shared drive. Another important function of this first phase was to host mission-critical documentation such as strategic goals, policies and procedures. Phase II of this project will focus on porting employee tasks into the centralized intranet environment. This development phase, which aims to replicate and automate the bulk of staff workflows within a content management system, will be a huge undertaking. <br /> <br /> We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?<br /> <br /> == Hands off! Best Practices and Top Ten Lists for Code Handoffs ==<br /> <br /> * Naomi Dushay, Stanford University Library, ndushay AT stanford DOT edu (as mouthpiece for multiple contributors)<br /> <br /> Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off?<br /> <br /> == How to be an effective evangelist for your open source project ==<br /> <br /> * Bess Sadler, Stanford University Library, bess@stanford.edu<br /> <br /> The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier. <br /> <br /> == Thoughts from an open source vendor - What makes a &quot;good&quot; vendor in a meritocracy? ==<br /> <br /> * Matt Zumwalt, Data Curation Experts / MediaShelf / Hydra Project, matt@curationexperts.com<br /> <br /> What is the role of vendors in open source? What should be the position of vendors in a meritocracy? What are the avenues for encouraging great vendors who contribute to open source communities in valuable ways? How you answer these questions has a huge impact on a community, and in order to formulate strong answers, you need to be well informed. Let’s glimpse at the business practicalities of this situation, beginning with 1) an overview of the viable profit models for open-source software, 2) some of the realities of vendor involvement in open source, and 3) an account of the ins &amp; outs of compensation &amp; equity structures within for-profit corporations.<br /> <br /> The topics of power &amp; influence, fairness, community participation, software quality, employment and personal profit are fair game, along with software licensing, support, sponsorship, closed source software and the role of sales people.<br /> <br /> This presentation will draw on personal experience from the past seven years spent bootstrapping and running MediaShelf, a small but prolific for-profit consulting company that focuses entirely on open source digital repository software. MediaShelf has played an active role in creating the Hydra Framework and continuously contributes to maintenance of Fedora and Blacklight. Those contributions have been funded through consulting contracts for authoring &amp; implementing open source software on behalf of organizations around the world.<br /> <br /> ==Occam’s Reader: A system that allows the sharing of eBooks via Interlibrary Loan==<br /> <br /> *Ryan Litsey, Texas Tech University, Ryan DOT Litsey AT ttu.edu<br /> *Kenny Ketner, Texas Tech University, Kenny DOT Ketner AT ttu.edu<br /> <br /> Occam’s Reader is a software platform that allows the transfer and sharing of electronic books between libraries via existing interlibrary loan software. Occam’s Reader allows libraries to meet the growing need to be able to share our electronic resources. In the ever-increasing digital world, many of our collection development plans now include eBook platforms. The problem with eBooks, however, is that they are resources that are locked into the home library. With Occam’s Reader we can continue the centuries-old tradition of resource sharing and also keep up with the changing digital landscape. <br /> <br /> <br /> == Using Puppet for configuration management when no two servers look alike ==<br /> * Eugene Vilensky, Senior Systems Administrator, Northwestern University Library, evilensky northwestern edu<br /> <br /> Configuration management is hot because it allows one to scale to thousands of machines, all of which look alike, and tightly manage changes across the nodes. Infrastructure as code, implement all changes programmatically, yadda yadda yadda.<br /> <br /> Unfortunately, servers which have gone unmanaged for a long time do not look very similar to each other. Variables come in many forms, usually because of some or all of the following: Who installed the server, where it was installed, where the image was sourced from, when it was installed, where additional packages were sourced, and what kind of software was hosted on it.<br /> <br /> Bringing such machines into your configuration management platform is no harder and no easier than some or all of the following options options: 1) blow such machines away and start from scratch, migrate your data. 2) Find the lowest common baseline between the current state and the ideal state and start the work there. 3) implement new features/services on existing unmanaged machines but manage the new features/services.<br /> <br /> I will describe our experiences at the library for all three options using the Puppet open-source tool on Enterprise Linux 5 and 6.<br /> <br /> == REST &lt;b&gt;IS&lt;/b&gt; Your Mobile Strategy ==<br /> <br /> * Richard Wolf, University of Illinois at Chicago, richwolf@uic.edu<br /> <br /> Mobile is the new hotness ... and you can't be one of the cool kids unless you've got your own mobile app ... but the road to mobility is daunting. I'll argue that it's actually easier than it seems ... and that the simplest way to mobility is to bring your data to the party, create a REST API around the data, tell developers about your API, and then let the magic happen. To make my argument concrete, I'll show (lord help me!) how to go from an interesting REST API to a fun iOS tool for librarians and the general public in twenty minutes.<br /> <br /> == ARCHITECTING ScholarSphere: How We Built a Repository App That Doesn't Feel Like Yet Another Janky Old Repository App ==<br /> <br /> * Dan Coughlin, Penn State University, danny@psu.edu<br /> * Mike Giarlo, Penn State University, michael@psu.edu<br /> <br /> ScholarSphere is a web application that allows the Penn State research community to deposit, share, and manage its scholarly works. It is also, as some of our users and our peers have observed, a repository app that feels much more like Google Docs or GitHub than earlier-generation repository applications. ScholarSphere is built upon the Hydra framework (Fedora Commons, Solr, Blacklight, Ruby on Rails), MySQL, Redis, Resque, FITS, ImageMagick, jQuery, Bootstrap, and FontAwesome. We'll talk about techniques we used to:<br /> <br /> * eliminate Fedora-isms in the application<br /> * model and expose RDF metadata in ways that users find unobtrusive<br /> * manage permissions via a UI widget that doesn't stab you in the face<br /> * harvest and connect controlled vocabularies (such as LCSH) to forms<br /> * make URIs cool<br /> * keep the app snappy without venturing into the architectural labyrinth of YAGNI<br /> * build and queue background jobs<br /> * expose social features and populate activity streams<br /> * tie checksum verification, characterization, and version control to the UI<br /> * let users upload and edit multiple files at once<br /> <br /> The application will be demonstrated; code will be shown; and we solemnly commit to showing ABSOLUTELY NO XML.<br /> <br /> ==Coding with Mittens==<br /> <br /> *Jim LeFager, DePaul University Library jlefager@depaul.edu<br /> <br /> <br /> Working in an environment where developers have restricted access to servers and development areas, or where you are primarily working in multiple hosted systems with limited access, can be a challenge when you are attempting to incorporate any new functionality or improve an existing one. Hosted web services present a benefit so that staff time is not dedicated to server maintenance and development, but customization can be difficult and at times impossible. In many cases, incorporating any current API functionality requires additional work besides the original development work which can be frustrating and inefficient. The result can be a Frankenstein monster of web services that is confusing to the user and difficult to navigate. <br /> <br /> This talk will focus on some effective best practices, and maybe not so great but necessary practices that we have adopted to develop and improve our user’s experience using javascript/jQuery and CSS to manipulate our hosted environments. This will include a review of available tools that allow collaborative development in the cloud, as well as examples of jQuery methods that have allowed us to take additional control of these hosted environments as well as track them using Google Analytics. Included will be examples from Springshare Campus Guides, CONTENTdm and other hosted web spaces that have been ‘hacked’ to improve the UI. <br /> <br /> <br /> == Hacking the DPLA ==<br /> * Nate Hill, Chattanooga Public Library, nathanielhill AT gmail.com<br /> * Sam Klein, Wikipedia, metasj AT gmail.com<br /> <br /> The Digital Public Library of America is a growing open-source platform to support digital libraries and archives of all kinds. DPLA-alpha is available for testing, with data from six initial Hubs. New APIs and data feeds are in development, with the next release scheduled for April. <br /> <br /> Come learn what we are doing, how to contribute or hack the DPLA roadmap, and how you (or your favorite institution) can draw from and publish through it. Larger institutions can join as a (content or service) hub, helping to aggregate and share metadata and services from across their {region, field, archive-type}. We will discuss current challenges and possibilities (UI and API suggestions wanted!), apps being built on the platform, and related digitization efforts.<br /> <br /> DPLA has a transparent community and planning process; new participants are always welcome. Half the time will be for suggestions and discussion. Please bring proposals, problems, partnerships and possible paradoxes to discuss.<br /> <br /> == Introduction to SilverStripe 3.0 ==<br /> <br /> * Ian Walls, University of Massachusetts Amherst, iwalls AT library DOT umass DOT edu<br /> <br /> SilverStripe is an open source Content Management System/development framework out of New Zealand, written in PHP, with a solid MVC structure. This presentation will cover everything you need to know to get started with SilverStripe, including<br /> * Features (and why you should consider SilverStripe)<br /> * Requirements &amp; Installation<br /> * Model-View-Controller<br /> * Key data types &amp; configuration settings<br /> * Modules<br /> * Where to start with customization<br /> * Community support and participation<br /> <br /> == Citation search in SOLR and second-order operators ==<br /> <br /> * Roman Chyla, Astrophysics Data System, roman.chyla AT (cfa.harvad.edu|gmail.com)<br /> <br /> Citation search is basically about connections (Is the paper read by a friend of mine more important than others? Get me a paper read by somebody who cites many papers/is cited by many papers?), but the implementation of the citation search is surprisingly useful in many other areas.<br /> <br /> I will show 'guts' of the new citation search for astrophysics, it is generic and can be applied recursively to any Lucene query. Some people would call it a second-order operation because it works with the results of the previous (search) function. The talk will see technical details of the special query class, its collectors, how to add a new search operator and how to influence relevance scores. Then you can type with me: friends_of(friends_of(cited_for(keyword:&quot;black holes&quot;) AND keyword:&quot;red dwarf&quot;))<br /> <br /> <br /> == Managing Segmented Images and Hierarchical Collections with Fedora-Commons and Solr ==<br /> <br /> * David Lacy, Villanova University, david DOT lacy AT villanova.edu<br /> <br /> Many of the resources within our digital library are split into parts -- newspapers, scrapbooks and journals being examples of collections of individual scanned pages. In some cases, groups of pages within a collection, or segments within a particular page, may also represent chapters or articles.<br /> <br /> We recently devised a procedure to extract these &quot;segmented resources&quot; into their own objects within our repository, and index them individually in our Discovery Layer.<br /> <br /> In this talk I will explain how we dissected and organized these newly created resources with an extension to our Fedora Model, and how we make them discoverable through Solr configurations that facilitate browsable hierarchical relationships and field-collapsed results that group items within relevant resources.<br /> <br /> == Google Analytics, Event Tracking and Discovery Tools==<br /> <br /> * Emily Lynema, North Carolina State University Libraries. ejlynema AT ncsu DOT edu<br /> * Adam Constabaris, North Carolina State University Libraries, ajconsta AT ncsu DOT edu<br /> <br /> The NCSU Libraries is using Google Analytics increasingly across its website as a replacement for usage tracking via Urchin. More recently, we have also begun to use the event tracking features in Google Analytics. This has allowed us to gather usage statistics for activities that don’t initiate new requests to the server, such as clicks that hide and show already-loaded content (as in many tabbed interfaces). Aggregating these events together with pageview tracking in Google Analytics presents a more unified picture of patron activity and can help improve design of tools like the library catalog. While assuming a basic understanding of the use of Google Analytics pageview tracking, this presentation will start with an introduction to the event tracking capabilities that may be less widely known. <br /> <br /> We’ll share library catalog usage data pulled from Google Analytics, including information about features that are common across the newest wave of catalog interfaces, such as tabbed content, Google Preview, and shelf browse. We will also cover the approach taken for the technical implementation of this data-intensive JavaScript event tracking.<br /> <br /> As a counterpart, we can demonstrate how we have begun to use Google Analytics event tracking in a proprietary vendor discovery tool (Serials Solutions Summon). While the same technical ideas govern this implementation, we can highlight the differences (read, challenges) inherent in utilizing this type of event tracking in vendor-owned application vs. a locally developed application.<br /> <br /> Along the way, hopefully you’ll learn a little about why you might (or might not) want to use Google Analytics event tracking yourself and see some interesting catalog usage stats.<br /> <br /> == Actions speak louder than words: Analyzing large-scale query logs to improve the research experience ==<br /> <br /> * Raman Chandrasekar, Serials Solutions, Raman DOT Chandrasekar AT serialssolutions DOT com<br /> * Ted Diamond, Serials Solutions, Ted DOT Diamond AT serialssolutions DOT com<br /> <br /> Analyzing anonymized query and click through logs leads to a better understanding of user behaviors and intentions and provides great opportunities to respond to users with an improved search experience. A large-scale provider of SaaS services, Serials Solutions is uniquely positioned to learn from the dataset of queries aggregated from the Summon service generated by millions of users at hundreds of libraries around the world.<br /> <br /> In this session, we will describe our Relevance Metrics Framework and provide examples of insights gained during its development and implementation. We will also cover recent product changes inspired by these insights. Chandra and Ted, from the Summon dev team, will share insights and outcomes from this ongoing process and highlight how analysis of large-scale query logs helps improve the academic research experience.<br /> <br /> == Supporting Gaming in the College Classroom == <br /> <br /> *Megan O'Neill, Albion College, moneill AT albion DOT edu<br /> <br /> Faculty are increasingly interested both in teaching with games and with gamifying their courses. Introducing digital games and game support for faculty through the library makes a lot of sense, but it comes with a thorny set of issues. This talk will discuss our library's initial steps toward creating a digital gamerspace and game support infrastructure in the library, including:<br /> 1) The scope and acquisitions decisions that make the most sense for us, and 2) Some difficulties we've discovered in trying to get our collection, physical- , digital- and head-space, and infrastructure up and going.<br /> There will also be an extremely brief overview of WHY we decided to teach with games and to support gamification, what (if anything) to do about mobile gaming, and where games in education might be going.<br /> <br /> == Codecraft ==<br /> <br /> * Devon Smith, OCLC Research, smithde@oclc.org<br /> <br /> We can think of and talk about software development as science, engineering, and craft. In this presentation, I'll talk about the craft aspect of software. From Wikipedia[1]: &quot;In English, to describe something as a craft is to describe it as lying somewhere between an art (which relies on talent and technique) and a science (which relies on knowledge). In this sense, the English word craft is roughly equivalent to the ancient Greek term techne.&quot; Of the questions who, what, where, why, when, and how, I will focus on why and how, with a minor in where.<br /> <br /> '''N.B.''': This will be a NON-TECHNICAL talk.<br /> <br /> [1] https://en.wikipedia.org/wiki/Craft#Classification<br /> <br /> == KnowBot: A Tool to Manage Reference and Beyond == <br /> <br /> * Sarah Park, Northwest Missouri State University<br /> * Hong Gyu Han, Northwest Missouri State University<br /> * Lori Mardis, Northwest Missouri State University<br /> <br /> Northwest Missouri State University has developed and used RefPole for collecting and analyzing reference statistics since 2005. RefPole was a tool to answer librarians’ needs to manage reference statistics and knowledge among librarians. It was an analysis tool for the library leaders to make decisions on library operations. RefPole was adequate for the internal use; however, it was developed for local access which keeps the collective reference knowledge from being shared beyond the desktop and from being accessed by students and faculty. <br /> <br /> In 2011, responding to growing internal and external need, the library has developed a web based knowledge base management system, KnowBot, in Ruby on Rail. KnowBot offers public searching, rating, cloud tagging, librarian, and reporting interfaces. With the additional public interfaces, it also extended reference services 24/7. Librarians can record responses to questions with graphics and multimedia. The reporting interface features not only the simple transactional data, but it also exhibits multi-dimensional analytic tool in real time.<br /> <br /> The presenters will demonstrate KnowBot; share the source code; and discuss the use of the knowledge base to answer the organizational and public need.<br /> <br /> == Creating a (mostly) integrated Patron Account with SirsiDynix Symphony and ILLiad ==<br /> <br /> * Emily Lynema, North Carolina State University Libraries, ejlynema AT ncsu DOT edu<br /> * Jason Raitz, North Carolina State University Libraries, jcraitz AT ncsu DOT edu<br /> <br /> IIn 2012, the NCSU Libraries at long last replaced a vendor “my account” tool that had been running unsupported for years. With the opportunity to create something new, one of the initial goals was a user experience that more seamlessly combined ILS data from SirsiDynix Symphony with ILL data from ILLiad. As a Kuali OLE beta partner, the NCSU Libraries is looking at an ILS migration within the next few years, so another goal was to build the interface on top of a standard so it would not have to be re-written as part of the migration. And the icing on the cake was a transition from a local Perl-based authentication system to the newer campus-wide Shibboleth authentication.<br /> <br /> This presentation will start with our design goals for a new user interface, include a demonstration, and describe the simple techniques used to provide a more integrated view of Symphony and ILLiad patron data. The backbone of the actual application is built using Zend’s PHP Framework and integrates eXtensible Catalog’s NCIP Toolkit to reach out to Symphony for patron data. In addition, we can talk about our successes (and difficulties) using jQuery Mobile to create a mobile view using the same underlying code as the web version. As one of our first Shibboleth applications here in the Libraries, this experience also taught us first-hand about some of the challenges of this type of single sign-on.<br /> <br /> == SKOS Name Authority in a DSpace Institutional Repository ==<br /> <br /> * Tom Johnson, Oregon State University, thomas.johnson@oregonstate.edu<br /> <br /> Name ambiguity is widespread in institutional repositories. Searching by author, users are typically greeted by a variety of misspellings and permutations of initials, collision between contributors with similar names, and other problems inherent in uncontrolled (often user-submitted) data. While DSpace has the technical capacity to use controlled names, it relies on outside authority files (from LoC, for example) to do the heavy lifting. For institutional authors, this leaves a major coverage gap and creates namespace pollution on a vast scale (try searching [http://authorities.loc.gov authorities.loc.gov] for &quot;Johnson, John&quot;, sometime). <br /> <br /> OSU is solving this problem with an institutionally scoped, low maintenance SKOS/FOAF &quot;name authority file&quot;. People in the IR are assigned URIs, names are maintained as skos:prefLabel, altLabel, or hiddenLabel. We've developed a simple Python application allowing staff to update individual &quot;records&quot;, and code on the DSpace side to access the dataset over SPARQL. This presentation will walk you through where we are now, limitations we've run into, and possibilities for the future.<br /> <br /> == Meta-Harvesting: Harvesting the Harvesters ==<br /> <br /> * Steven Anderson, Boston Public Library, sanderson AT bpl DOT org<br /> * Eben English, Boston Public Library, eenglish AT bpl DOT org<br /> <br /> The emerging Digital Public Library of America (http://dp.la/) has proposed to aggregate digital content for search and discovery from several regional &quot;service hubs&quot; that will provide metadata via an as-yet-unspecified harvest process. As these service hubs are already harvesters of digital content from myriad sources themselves, the potential for &quot;telephone game&quot;-esque data loss and/or transmutation is a significant danger.<br /> <br /> This talk will discuss the experience of Digital Commonwealth (http://www.digitalcommonwealth.org/), a statewide digital repository currently in the process of being revamped, refactored, and redesigned by the Boston Public Library using the Hydra Framework. The repository, which aggregates data from over 20 institutions (some of which are themselves aggregators), is also undergoing a massive metadata cleanup effort as records are prepared to be ingested into the DPLA as one of the regional service hubs. Topics will include automated and manual processes for data crosswalking and cleanup, advanced OAI-PMH chops, and the implications of the (at this time still-emerging) metadata standards and APIs being created by the DPLA.<br /> <br /> Every crosswalk, transformation, migration, harvest, or export/ingest of metadata requires informed decision making and precise attention to detail. This talk will provide insight into key decision points and potential quagmires, as well as a discussion of the challenges of dealing with heterogeneous data from a wide variety of institutions.<br /> <br /> == Pay No More Than £3 // DIY Digital Curation ==<br /> <br /> * Chris Fitzpatrick, World Maritime University, cf AT wmu DOT se<br /> <br /> Are you a small library or archive? &lt;br&gt;<br /> Do you feel you are being held back by limited technical resources?&lt;br&gt;<br /> Tired of waiting around for the Google Books Library people to reply to your emails? &lt;br&gt;<br /> <br /> Join the club. Open-source software, hackerspaces, dirt cheap storage, cloud computing, and social media make it possible for any institution to start curating digitally. Today.<br /> This talk will cover some of the guerrilla tactics being employed to drag a small university's large collection into the internet age. <br /> <br /> Topics will include: <br /> *Cheap and effective document scanning methods.<br /> *Valuable resources found at your local hackerspace / makerspace / fablab.<br /> *Metadata enrichment for the not-so-rich and NLP for the people.<br /> *Utilizing social media to crowdsource your collection building.<br /> *How to post-process, OCR, PDF, and ePub your documents using Free software.<br /> *Ways to build out a digital repository with no servers, code, or large 2-year grants required. (ok, maybe some code).<br /> <br /> == IIIF: One Image Delivery API to Rule Them All ==<br /> <br /> * Willy Mene, Stanford University Libraries, wmene AT stanford DOT edu<br /> * Stuart Snydman, Stanford University Libraries, snydman AT stanford DOT edu<br /> <br /> The International Image Interoperability Framework was conceived of by a group of research and national libraries determined to achieve the holy grail of seamless sharing and reuse of images in digital image repositories and applications. By converging on common API’s for image delivery, metadata transmission and search, it is catalyzing the development of a new wave of interoperable image delivery software that will surpass the current crop of image viewers, page turners, and navigation systems, and in so doing give scholars an unprecedented level of consistent and rich access to image-based resources across participating repositories.<br /> <br /> The IIIF Image API (http://library.stanford.edu/iiif/image-api) specifies a web service that returns an image in response to a standard http or https request. The URL can specify the region, size, rotation, quality characteristics and format of the requested image. A URL can also be constructed to request basic technical information about the image to support client applications. The API could be adopted by any image repository or service, and can be used to retrieve static images in response to a properly constructed URL.<br /> <br /> In this presentation we will review version 1 of the IIIF image api and validator, demonstrate applications by daring early adopters, and encourage widespread adoption.<br /> <br /> == Data-Driven Documents: Visualizing library data with D3.js ==<br /> <br /> * Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu<br /> <br /> Several JavaScript libraries have emerged over the past few years for creating rich, interactive visualizations using web standards. Few are as powerful and flexible as D3.js[1]. D3 stands apart by merging web standards with a rich API and a unique approach to binding data to DOM elements, allowing you to apply data-driven transformations to a document. This emphasis on data over presentation has made D3 very popular; D3 is used by several prominent organizations including the New York Times[2], GOV.UK[3], and Trulia[4].<br /> <br /> Power usually comes at a cost, and D3 makes you pay with a steeper learning curve than many alternatives. In this talk, I will get you over the hump by introducing the core construct of D3, the Data-Join. I will also discuss when you might want to use D3.js, share some examples, and explore some advanced utilities like scales and shapes. I will close with a brief overview of how we are successfully using D3 at NCSU[5] and why investing time in learning D3 might make sense for your library.<br /> <br /> *[1]http://d3js.org/<br /> *[2]http://www.nytimes.com/interactive/2012/08/24/us/drought-crops.html<br /> *[3]https://www.gov.uk/performance/dashboard<br /> *[4]http://trends.truliablog.com/vis/pricerange-boston/<br /> *[5]http://www.lib.ncsu.edu/dli/projects/spaceassesstool<br /> <br /> == ''n'' Characters in Search of an Author ==<br /> <br /> * Jay Luker, IT Specialist, Smithsonian Astrophysics Data System, jluker@cfa.harvard.edu<br /> <br /> When it comes to author names the disconnect between our metadata and what a user might enter into a search box presents challenges when trying to maximize both precision and recall [0]. When indexing a paper written by &quot;Wäterwheels, A&quot; a goal should be to preserve as much as possible the original information. However, users searching by author name may frequently omit the diaeresis and search for simply, &quot;Waterwheels&quot;. The reverse of this scenario is also possible, i.e., your decrepit metadata contains only the ASCII, &quot;Supybot, Zoia&quot;, whereas the user enters, &quot;Supybot, Zóia&quot;. If recall is your highest priority the simple solution is to always downgrade to ASCII when indexing and querying. However this strategy sacrifices precision, as you will be unable to provide an &quot;exact&quot; search, necessary in cases where &quot;Hacker, J&quot; and &quot;Häcker, J&quot; really are two distinct authors.<br /> <br /> This talk will describe the strategy ADS[1] has devised for addressing common and edge-case problems faced when dealing with author name indexing and searching. I will cover the approach we devised to not only the transliteration issue described above, but also how we deal with author initials vs. full first and/or middle names, authors who have published under different forms of their name, authors who change their names (wha? people get married?!). Our implementation relies on Solr/Lucene[2], but my goal is an 80/20 mix of high- vs. low-level details to keep things both useful and stackgnostic [3].<br /> <br /> *[0] http://en.wikipedia.org/wiki/Precision_and_recall<br /> *[1] http://www.adsabs.harvard.edu/<br /> *[2] http://lucene.apache.org/solr/<br /> *[3] http://en.wikipedia.org/wiki/Portmanteau<br /> <br /> == But, does it all still work : Testing Drupal with simpletest and casperjs ==<br /> <br /> * David Kinzer - Lead Developer, Jenkins Law Library, dkinzer@jenkinslaw.org<br /> * Chad Nelson - Developer, Jenkins Law Library, cnelson@jenkinslaw.org<br /> <br /> Most developers know that they should be writing tests along with their code, but not every developer knows how or where to get started. This talk will walk through the nuts and bolts of the testing a medium-sized Drupal site with many integrated moving parts. We’ll talk about unit testing of individual functions with [http://www.simpletest.org/en/overview.html SimpleTest] (and how that has changed how we write functions), functional testing of the user interface with [http://casperjs.org/ casperjs]. We will discuss automating deployment with [http://www.phing.info/ phing], [http://drupal.org/project/drush drush], [http://jenkins-ci.org/ jenkins-ci] &amp; github, which, combined with our tests, removes the “hold-your-breath” feeling before updating our live site. <br /> <br /> <br /> [[Category:Code4Lib2013]]<br /> <br /> == Relations, Recommendations and PostgreSQL ==<br /> <br /> * William Denton, Web Librarian, York University, wdenton@yorku.ca<br /> * Dan Scott, Systems Librarian, Laurentian University, dscott@laurentian.ca<br /> <br /> In 2012, a ragtag group of library hackers from various Ontario <br /> universities, funded with only train tickets and fueled with Tim Hortons <br /> coffee, assembled under the Scholars Portal banner to build a common <br /> circulation data repository and recommendation engine: the Scholars <br /> Portal Library Usage-based Recommendation Engine (SPLURGE). PostgreSQL, <br /> the emerging darling of the old-school relational database world, is the <br /> heart of SPLURGE, and the circulation data for Ontario's 400,000 <br /> university students is its blood. Two of the contributors to this effort explore the PostgreSQL features <br /> that SPLURGE uses to ease administration efforts, simplify application <br /> development, and deliver high performance results. If you don't use <br /> PostgreSQL for your data, you might want to try it after this <br /> presentation; if you already do, you'll pick up some new tips and tricks.<br /> <br /> <br /> == A Cure for Romnesia: Site Story Web-Archiving ==<br /> <br /> * Harihar Shankar, Research Library, Los Alamos National Laboratory, harihar@lanl.gov<br /> <br /> The web changes constantly, erasing both inconvenient facts and<br /> fictions. At web-scale, preservation organizations cannot be expected<br /> to keep up by using traditional crawling, and they already miss many<br /> important versions. The cure for this is to capture the interactions<br /> between real browsers and the server, and push these into an archive<br /> for safe keeping rather than trying to guess when pages change.<br /> <br /> Every time the Apache Web Server sends data to a browser, SiteStory’s<br /> Apache Module also pushes this data to the SiteStory Web Archive. The<br /> same version of a resource will not be archived more than once, no<br /> matter how many times it has been requested. The resulting archive is<br /> effectively representative of a server's entire history, although<br /> versions of resources that are never requested by a browser will also<br /> never be archived.<br /> <br /> In this presentation I will give an overview of SiteStory, an<br /> Open-Source project written in Java that runs as an application under<br /> Tomcat 6 or greater. SiteStory’s Apache Module is written in C. I will<br /> also demonstrate the TimeMap tool that visualizes versions of a<br /> resource available in the SiteStory archive. The TimeMap tool is a<br /> Firefox browser extension that plots versions of a resource on a<br /> SIMILE timeline. Since the tools uses the Memento protocol, it can<br /> also display versions of resources available in Memento compliant web<br /> archives and content management systems.<br /> <br /> == Practical Relevance Ranking for 10 million books. ==<br /> <br /> * Tom Burton-West, University of Michigan Library, tburtonw@umich.edu<br /> <br /> [http://www.hathitrust.org/ HathiTrust Full-text search] indexes the full-text and metadata for over 10 million books. There are many challenges in tuning relevance ranking for a collection of this size. This talk will discuss some of the underlying issues, some of our experiments to improve relevance ranking, and our ongoing efforts to develop a principled framework for testing changes to relevance ranking.<br /> <br /> Some of the topics covered will include:<br /> <br /> * Length normalization for indexing the full-text of book-length documents<br /> * Indexing granularity for books<br /> <br /> *Testing new features in Solr 4.0:<br /> **New ranking formulas that should work better with book-length documents: BM25 and DFR.<br /> **Grouping/Field Collapsing. Can we index 3 billion pages and then use Solr's field collapsing feature to rank books according to the most relevant page(s)?<br /> **Finite State Automota/Block Trees for storing the in-memory index to the index. Will this allow us to allow wildcards/truncation despite over 2 billion unique terms per index?<br /> <br /> *Relevance testing methodologies:Query log analysis, Click models, Interleaving, A/B testing, and Test collection based evaluation.<br /> <br /> *Testing of a new high-performance storage system to be installed in early 2013. We will report on any tests we are able to run prior to conference time.<br /> <br /> == Browser/Javascript Integration Testing with Ruby ==<br /> <br /> * Jessie Keck, Stanford University, jkeck at stanford dot edu<br /> <br /> It's near impossible to build a rich web application without javascript. We have a lot of great patterns to follow, such as progressive enhancement, to make sure our rich web applications are usable, accessible, and testable. However; when javascript is involved the possibility exists that bugs can be introduced that won't get caught by most unit and integration testing frameworks.<br /> <br /> <br /> This is where Watir (pronounced water) comes in. Watir can be used with popular ruby testing frameworks like RSpec and Capybara. This talk will show how to use the combination of these tools to write RSpec tests using Watir to spin up an application in a variety of browsers, navigate the application, and make assertions about the page using Capybara.<br /> <br /> <br /> Tests using Watir are written in ruby but they don't necessarily need to test ruby application. You can test any application that you can point a browser at, so there are a wide variety of potential uses for tests written with Watir.<br /> <br /> == Immanentizing the Google ==<br /> <br /> * Will Sexton, Duke University Libraries, will.sexton@duke.edu<br /> * Sean Aery, Duke University Libraries, sean.aery@duke.edu<br /> <br /> We're using a &quot;Google-as-a-Service&quot; approach to reduce the complexity and cost of maintaining a structured-data discovery platform for digitized collections and other library-generated content. Our work picks up from a paper in the code4lib Journal by NCSU's Jason Ronallo [1], introducing the idea of embedded schema.org HTML microdata for library digital collections. We've extended our schema.org/RDFa Lite implementation by using Google Site Search to develop a customized interface. In our talk, we'll demonstrate how to set up an instance of Site Search, how to customize the display of results, and how to use the platform's filtering, sorting and other useful functions. We'll also report on our analysis of usage data, and discuss our strategy for scaling the system to support global site search in an upcoming library-wide CMS migration project.<br /> <br /> [1] [http://journal.code4lib.org/articles/6400 &quot;HTML5 Microdata and Schema.org&quot;, code4lib #16]<br /> <br /> == Evolving Towards a Consortium MARCR Redis Datastore ==<br /> <br /> * Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu<br /> * Sheila Yeh, University of Denver, Sheila.Yeh@du.edu<br /> <br /> The current state of technology in library automation is not keeping pace with the explosive growth in information storage and retrieval system. The lag costs institutions as well as users’ resource discovery. To address this problem, we should look into how successfully enterprise such as Craigslist and StackOverflow manage and scale their enormous volume of data. The key lies in the Redis, a NoSQL open source advanced key-value data structure server. Therefore, Colorado College and the University of Denver, along with the Colorado Alliance of Research Libraries are exploring and co-developing a MARCR Redis Datastore. It is a peer-to-peer bibliographic datastore, modeled using the Library of Congress Bibliographic Framework's new Linked Data based MARC 21 replacement, called MARCR (MARC Resources). The structure of MARCR leads itself to an advanced Consortium catalog where a Work is cataloged once and multiple institutions have complete control over their own Instances of the Work, de-duplicating cataloging efforts while supporting real-time resource sharing between the Instances. Control, access, and discovery of records in the proposed MARCR Redis Datastore are provided through lightweight HTML5 responsive apps built with Django, Bootstrap, and KnockoutJS that also integrate with both open-source and commercial discovery products.<br /> <br /> Redis offers many advantages for a shared MARCR bibliographic datastore, such as speed, scalability, and ease-of-deployment. Especially it can support multiple cloud models that benefits institution of various size and capital. We will demonstrate a MVP (Minimal Viable Product) iteration of this MARCR Datastore using the transformed MARC 21 records from Colorado College and the University of Denver into Redis with coordination by Colorado Alliance of Research Libraries.<br /> <br /> == Take Your Content and Shove It ==<br /> <br /> * Eric Frierson*, EBSCO Publishing, efrierson@ebscohost.com<br /> <br /> Public services librarians have experimented getting out of the library. For example, the 'embedded librarian' model puts the librarian in class with students, offering help and advice throughout the semester at the point of need. Digital services have also found their way into virtual classrooms by way of links from the course management system (e.g., Blackboard, Moodle) and the occasional embedded search box that serves as a portal into the library's search solution.<br /> <br /> With the release of discovery services and their associated APIs, we can do more. Rather than linking back to the library, we can take our resources and push them into the learning experience, allowing them to escape the library website silo altogether. Imagine a professor being able to search library resources and add items to their course website without ever leaving their CMS, or a student adding items to a folder that shows up in their campus dashboard. What if we could tie the use of library resources to student success in the classroom by leveraging user data from CMS tools? In this session, I will briefly describe how APIs might make these scenarios possible, but then facilitate a discussion on where else we could shove our resources. I hope to initiate a few development projects along these lines.<br /> <br /> == On Top of Discovery (All Covered with Customizations) ==<br /> <br /> * Scott Hanrath, University of Kansas Librarires, shanrath@ku.edu<br /> <br /> On Top of Discovery (All Covered with Customizations)<br /> <br /> How and why we've customized the front-end of our vendor library discovery system (Primo) to improve the user experience and integrate with local systems using dollops of JavaScript, a pinch of JSONP, and a smattering of both vendor and simple homegrown APIs. I'll talk about techniques for adding more AJAX to an already AJAX-intensive interface that you don't fully control (and how a few underlying changes could make it easier) and reflect on our meatball-retention odds in the event that somebody sneezes and the underlying interface changes.<br /> <br /> Features to be discussed include improving the display of quasi-FRBRized records in search results through subtracting metadata here and adding metadata there, adding a 'did-you-mean' option in an attempt to steer users toward using Boolean operators in the way the system demands, adding fine-grained event tracking with Google Analytics, and porting existing add-ons like special collection requests, augmented stacks locations, and demand-driven acquisitions requests from our last-generation OPAC.<br /> <br /> == EAD without XSLT: A Practical New Approach to Web-Based Finding Aids ==<br /> <br /> * Trevor Thornton, New York Public Library, trevorthornton@nypl.org<br /> <br /> The New York Public Library is reengineering its system for delivering archival finding aids on the Web. The foundation of this system is a data management application, written in Rails, within which collections and their components are managed as associated model instances, and descriptive data is stored natively as JSON and HTML. Front-end applications interact with the back-end via a flexible API that is capable of returning any part of the description at any level. This approach provides a number of benefits over the traditional XML/XSLT approach:<br /> <br /> * Data is stored natively in the format in which it is needed by the front-end application, making rendering much faster<br /> * Finding aid data can be lazy-loaded via AJAX requests<br /> * Enables presentation of the archival description beyond the traditional finding aid structure (alternate arrangements, visualizations, etc.)<br /> * Links to digital assets can be maintained independently of archival description<br /> * Data cleanup and normalization can be accomplished during and/or after ingest of original data into the system, ensuring data quality and consistency<br /> * Data is stored in a schema-neutral format, enabling easy transformation into other formats as required (e.g. RDF for semantic web applications, future version(s) of EAD schema for harvesting, etc.)<br /> <br /> In this session I will describe the architecture of this system and its data model, and discuss the challenges presented in the design process.<br /> <br /> == Primo / Blackboard Plugin Adaptor Development at Northwestern ==<br /> <br /> * Michael North, Northwestern University Libraries, m-north@northwestern.edu<br /> <br /> The two most visited websites on campus are the Blackboard Course Management System (CMS) site and the Library Discovery Webpage (powered by Primo). These two sites were perfect for a collaborative project to share functionality between themselves to the benefit of faculty and students. <br /> <br /> This collaborative project (using Java, API's, x-services) was successful in integrating the Library Primo resource records and e-Shelf folders, with Blackboard's Course Documents webpages for faculty to use in organizing student's study resources. First we developed a &quot;push&quot; feature used to push individual resources from Primo &quot;into&quot; Blackboard. This is a static link . Second, we created a &quot;pull&quot; feature whereby an entire Primo e-Shelf folder (containing sub-folders and resource records) can be pulled &quot;into&quot; Blackboard. This is a dynamic link. These two functions result in the Blackboard Course Documents page having Primo functionality with either dynamic or static resource links. <br /> <br /> This session will share an overview of the project, coding structure, and the technical hurdles that needed to be overcome to combine functionality between two major academically used application products.<br /> <br /> == Relishing Quality Assurance Testing with Cucumber ==<br /> <br /> *Joseph Dalton, The New York Public Library, josephdalton AT nypl DOT org<br /> <br /> For those starting on a test-driven development path, the plethora of options for QA testing can also be overwhelming, ranging from writing user stories and simple acceptance tests, to running automated tests with Cucumber and Gherkin (and optionally making these more visible to stakeholders with Relish), to utilizing complex, enterprise-level tools like Quality Center to model business processes. <br /> <br /> Although libraries are usually, and sometimes emphatically so, not profit-driven institutions, this doesn't have to mean there can't be a valid role for software quality assurance within our development environments. We've all heard &quot;any test is better than no tests at all,&quot; but how do we effectively encourage our own institutions to embrace a test-driven development path and quality-assurance testing when, unlike businesses, our organizations generally aren't tasked with obvious quality-drivers like generating a profit, ROI, etc? <br /> <br /> In this presentation I'll discuss some of the steps the New York Public Library has recently taken to define and develop a QA/Testing framework, in the context of the Library's recent adoption of Agile development practices for its Digital Repository and other project teams.<br /> <br /> == I woke up / fell out of bed / checked my mail / and what I read... : PHP to Java to NCIP to ... ==<br /> <br /> * John Bodfish, OCLC – bodfishj@oclc.org<br /> * Michelle Suranofsky, Lehigh University – mis306@lehigh.edu<br /> <br /> The trailer:<br /> [http://www.youtube.com/watch?v=HCJ0dmW5YEs YouTube video]<br /> <br /> It's 10 a.m. and your inbox has an 'Urgent' message from the State Librarian asking for an update on the “NCIP thing” for the statewide project first mentioned (to you) yesterday. You know there’s an open source “NCIP Toolkit” which supports the variety of systems involved in your statewide project, but you’ve also heard it’s pure Java and that’s not your cuppa. Sure it supports discovery with multiple ILS types, as well as resource sharing, patron empowerment, etc. etc. but is it possible to bridge those worlds? After a few minutes of searching you have a plan for ticking-off the “multi-vendor NCIP support” box on the project requirements. We’ll demonstrate a proof-of-concept implementation for PHP developers and report on the issues we encountered and our solutions.<br /> <br /> == Powering Complicated Web Form in Rails Using XML == <br /> <br /> * Kristopher Kelly, New York Public Library, kristopherkelly@nypl.org<br /> <br /> The New York Public Library recently launched the first phase of its new Metadata Management System, created in-house to create MODS-based metadata for digital assets. Moving from an idiosyncratic database design, the NYPL wanted to use a more standard format. Adopting MODS and XML led to the question of how to store the data. We chose to attempt to store XML in the database and edit it through a web form. Storing bibliographic data in such a way might seem counter-intuitive, but it has proven to solve more problems than it has created. <br /> <br /> In this session, I will discuss how we were able to power a complicated form with XML while improving usability and overall performance. <br /> <br /> == Message Queues: Event Driven Architecture for NYPL's repository platform ==<br /> <br /> * Jason Varghese, New York Public Library, jason dot varghese at nypl.org<br /> <br /> At the New York Public Library, the digital repository continues to grow at an astonishing rate with storage soon to reach petabyte range. As an increasing amount of content is produced, generated, or acquired, workflow automation and scalability became increasingly important. Workflow involves several organizational units using multiple systems. As a result, reducing the dependencies between our various systems was an important criteria. The message queue enables us to design an event driven system built from a suite of lightweight and interoperable REST-based services. Benefits include traditional drivers such as loose coupling, interoperability between heterogeneous systems, improving application scalability, and many more benefits that will be explored in this talk. <br /> <br /> == Synching up at Web Scale: the NISO/OAI ResourceSync Effort ==<br /> <br /> * Nettie Lagace, National Information Standards Organization (NISO), nettie AT niso DOT org <br /> <br /> It's increasingly the case that to better serve users in a dynamic Web environment, it's desirable to synchronize large-scale web resources accurately, and in real time. However, many current system designs cope with the lack of a good available solution to this requirement by de-emphasizing current coverage or by using tools to manage crawl scheduling. The NISO/OAI ResourceSync effort, funded by the Sloan Foundation and JISC, is currently designing an solution approach that is aligned with general Web Architecture and is targeted at different communities, particularly those in the areas of cultural heritage and research.<br /> <br /> The ResourceSync working group has been under way since early 2012, and expects to have its beta draft specification available for public review and testing by the time the Code4Lib conference takes place. This talk will outline the problem cases, the technical approach and reasoning taken by the working group, and invite feedback from the Code4Lib audience.<br /> <br /> == The Care and Feeding of a Crowd ==<br /> <br /> * Shawn Averkamp, University of Iowa, shawn-averkamp at uiowa.edu<br /> * Matthew Butler, University of Iowa, matthew-butler at uiowa.edu<br /> <br /> After a low-tech experiment in crowdsourced transcription grew into a surprisingly successful library initiative and demanded new commitments to user engagement, we found ourselves looking for a more efficient and user-friendly solution. We customized CHNM’s Scripto community transcription tool and various other Omeka plugins to develop a new site: DIYHistory.<br /> <br /> We often receive questions about the technical side of both platforms, usually (to our dismay) from libraries who already assume they don't have the IT resources to pursue their own crowdsourcing initiatives. But we found that the software makes up only half of the recipe for success. Do you have compelling content? A long-term commitment to engaging with your users? Are you ready to promote your project far and wide? If so, then deploying a crowdsourcing initiative may be easier than you think.<br /> <br /> Our very small development team, which consisted of a healthy mix of technologists and other stakeholders, worked closely and collaboratively on all aspects of the site. We’ll talk about customizing open-source software--how we scaled up functionality and scaled back design to improve user experience and production-level workflows--and how that process served to gently introduce collaborative software practices, such as using Git for version control, into a small, but agile, organization ready to grow. Finally, we'll share our transcription starter kit of forked Scipto and Omeka code and associated documentation for those interested in doing it themselves.<br /> <br /> == Linked Open Communism: Better discovery through data dis- and re- aggregation ==<br /> <br /> * Corey A Harper, New York University, corey dot harper at nyu dot edu<br /> <br /> Current library search interfaces focus on books, journals and articles but offer little access to related entities, such as people, places, and events. These entities are generally only represented as attributes of other metadata records. Linked data can power interfaces that surface these entities as first-class resources, integrating them into results alongside library materials. <br /> <br /> This presentation will describe research into such an interface for exploring a particular subject area: the history of the Communist Party &amp; labor movements in the US. A triple store was seeded by 1,600 EAD records from NYU's Tamiment Library and Wagner Labor Archives. Based on access points in the finding aids, the store was further populated with data from various sources, including MARC, id.loc, VIAF, and dbpedia. Identifiers are being assigned for a wide array of typed entities, and triples can then be re-assembled into new entity &quot;records&quot;. These new records will be loaded into a discovery interface that will allow typical keyword searching across *all* contained entities, show links between entities, and include faceting on entity types.<br /> <br /> It is hoped that this prototype will be a model for a new kind of interface to library, archive &amp; museum metadata targeted to particular subject domains, and could inform the development of a similar dis- and re- aggregation approach for entire library collections.<br /> <br /> == Building a Metadata Lab for LIS Students ==<br /> <br /> * Margaret Kipp, University of Wisconsin Milwaukee, kipp at uwm dot edu<br /> <br /> Teaching metadata and linked data concepts to MLIS students requires more than creating basic metadata records, it also requires an understanding of how metadata fits into the library workflow and how data entry into metadata and cataloguing tools works in practice. We are developing a metadata lab for use in teaching information organisation related courses to MLIS students. Currently we are using open source software for the lab including Koha--ILS, Omeka--digital library tool and 4store--RDF triple store. The preliminary tools are hosted on LAMP servers and will be supplemented with additional software as we expand our lab. This presentation will report on the results of setting up the first few software packages for the lab and their use in teaching various courses including an introductory course in information organisation, a metadata course, and a course on linked data, Semantic Web and mashups. One of the goals of this session would be to discuss methods for bridging gaps between academic and practical work with metadata.<br /> <br /> <br /> ==Feed - The HathiTrust Ingest Toolkit==<br /> * Ryan Rotter, University of Michigan, rrotter AT umich DOT edu<br /> <br /> HathiTrust has a mission of ensuring the long-term preservation and accessibility of materials in the archive. Ensuring consistency among materials from different sources is one way we do this; it ensures that tools such as large scale search and PageTurner don't need to be concerned with where the content originated from and that it will be possible to undertake format migrations in the future. To ensure consistency, we have very specific and stringent standards including (but not limited to) the following areas:<br /> <br /> * Item identifiers (i.e. how each individual submitted item is identified and named)<br /> * Package layout (file names, directory structure, etc.)<br /> * Image technical characteristics (file format, resolution, color depth, etc.)<br /> * Image metadata (scanning time, scanning artist, etc.)<br /> * Source METS file comprising MARC, PREMIS, package contents and structMap, optionally with page numbers and page tags<br /> <br /> We have chosen not to accept submissions in arbitrary formats for a couple of reasons. Unfortunately we just don't have the resources to create custom transformations for all sources of content, and if we created generic transformations that could accept data in a wide variety of formats there would most likely be some data loss in the transformation.<br /> <br /> Therefore we have chosen to provide the ingest tools to the library community as a set of building blocks to help you build and validate submission packages that meet the standards while at the same time allowing you to preserve images without loss of quality and include any metadata that you want to preserve.<br /> <br /> ==Roses are ff0000, Violets are 0000ff DeLaMare is throwing a Hackathon and so should you!==<br /> <br /> * Chrissy Klenke, University of Nevada, Reno, cklenke@unr.edu<br /> * Nick Crowl, University of Nevada, Reno, ncrowl@unr.edu<br /> <br /> Hack 4 Reno is a 24-hour hackathon, where teams use local data to build applications that benefit the local community. Co-hosted by Reno Collective and the DeLaMare Science and Engineering Library, and sponsored by the City of Reno which generously provides the data, the teams, made up up of coders, designers, writers, and more, get to hack away for 24-hours, creating, collaborating, and having fun with it all: http://hack4reno.com/ <br /> <br /> The Reno Collective is Reno’s premiere co-working space for freelancers, designers, programmers, entrepreneurs, and startups. The DeLaMare Science and Engineering Library (DLM) at the University of Nevada, Reno is fast becoming the bridge between students, faculty, and members of its greater community of Reno Collective, Hack4Reno, Bridewire Makerspace, and the Code for American Reno Brigade. <br /> <br /> Come hear about the hackathon, the projects created out of this event, and a glimpse of a few of the innovative projects created in collaboration with the DeLaMare Library. Robotics kits, 3D printers, drone quadricopters, lockpicking workshops and kits, bootcamps and 24-hour hackathons are just the start! <br /> <br /> <br /> == Stuffing the Repository: An Advanced Dive Into Object Handling in Hydra ==<br /> <br /> * Steven Anderson, Boston Public Library, sanderson AT bpl DOT org<br /> * Eben English, Boston Public Library, eenglish AT bpl DOT org<br /> <br /> This topic focuses on some advanced techniques for dealing with digital objects created for a repository. While all examples presented will be in the Hydra framework, the theory of what is presented is applicable to non-Hydra solutions. Specific topics include:<br /> <br /> * Client side MD5 checksumming: While an Ajax file upload is fairly simple nowadays, verifying that the file doesn't become corrupted during transmission to the server is often overlooked. A method to calculate the MD5 checksum via the client browser before the file is transmitted over the network will be presented.<br /> <br /> * Object Modeling Inheritance: There are many different theories regarding content modeling in the wild, from &quot;one model to rule them all&quot; to extreme granularity. Here we will outline an approach to modeling content inspired by OOP, using specific content type classes that inherit from a set of more generic content models.<br /> <br /> * Hydra Models as a Rails Engine: In order to facilitate sharing of content models between multiple Hydra code bases, a completely separate and independent Ruby on Rails Engine to express content models has been developed. This unique approach offers tremendous potential for easily sharing and re-using pre-configured content models in a Hydra Head simply by installing a gem.<br /> <br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_talks_proposals&diff=27673 2012-10-29T17:26:36Z

<p>Ndushay: /* Solr Testing Is Easy with Rspec-Solr Gem */</p> <hr /> <div>Deadline for talk submission is ''Friday, November 2'' at 5pm PT.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br /> * tools (some cool new software, software library or integration platform)<br /> * specs (how to get the most out of some protocols, or proposals for new ones)<br /> * challenges (one or more big problems we should collectively address)<br /> <br /> The community will vote on proposals using the criteria of:<br /> * usefulness<br /> * newness<br /> * geekiness<br /> * uniqueness<br /> * awesomeness<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> == Talk Title ==<br /> <br /> * Speaker's name, affiliation, and email address<br /> * Second speaker's name, affiliation, email address, if applicable<br /> <br /> Abstract of no more than 500 words.<br /> &lt;/pre&gt;<br /> <br /> == Modernizing VuFind with Zend Framework 2 ==<br /> <br /> * Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu<br /> <br /> When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.<br /> <br /> == Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==<br /> <br /> * [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br /> <br /> Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby. <br /> Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]? <br /> It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.<br /> So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?<br /> This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.<br /> <br /> == Drupal 8 Preview — Symfony and Twig ==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.<br /> <br /> It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.<br /> <br /> Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.<br /> <br /> == Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==<br /> <br /> * Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu<br /> <br /> Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &quot;Let's digitize these together and make them one big awesome project to support public urban history&quot;? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of &quot;grand ideas crushed by technological limitations&quot; and &quot;projects on the right track&quot; to follow. <br /> <br /> == ResCarta Tools building a standard format for audio archiving, discovery and display ==<br /> <br /> * [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org<br /> <br /> The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit. <br /> <br /> Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.<br /> <br /> ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! <br /> <br /> You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old) <br /> <br /> == Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==<br /> <br /> * Michael Doran, University of Texas at Arlington, doran@uta.edu<br /> <br /> This presentation will use a seemingly simple data point, the &quot;format&quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. <br /> <br /> I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session. <br /> <br /> == Touch Kiosk 2: Piezoelectric Boogaloo ==<br /> <br /> * Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu<br /> <br /> At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.<br /> <br /> In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.<br /> <br /> I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.<br /> <br /> [1] http://journal.code4lib.org/articles/5832<br /> <br /> == Wayfinding in a Cloud: Location Service for libraries ==<br /> <br /> * Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi<br /> <br /> Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.<br /> <br /> The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.<br /> <br /> The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.<br /> <br /> == Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.<br /> * Automatically inventory a collection of documents or images to be uploaded<br /> * Generate a spreadsheet for metadata capture based on the inventory<br /> * Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested<br /> * Validate the contents of ingest folders prior to initiating the ingest to DSpace<br /> * Present users with a simple, web-based form to initiate the batch ingest process<br /> <br /> The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections. <br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == Quality Assurance Reports for DSpace Collections ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection<br /> <br /> These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.<br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==<br /> <br /> * Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca<br /> * Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca<br /> <br /> In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.<br /> <br /> See article: http://journal.code4lib.org/articles/7470<br /> <br /> == HTML5 Video Now! ==<br /> <br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> <br /> How to get started using HTML5 video right now, including gotchas, tips, tricks, and the future of video on the Web.<br /> <br /> == Hybrid Archival Collections Using Blacklight and Hydra ==<br /> <br /> * Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org<br /> <br /> At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.<br /> <br /> Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.<br /> <br /> == Making the Web Accessible through Solid Design ==<br /> <br /> * [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp; Archives<br /> <br /> In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.<br /> <br /> While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.<br /> <br /> == Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp; Much More ==<br /> <br /> * Steven Marsden, Ryerson University Library &amp; Archives, steven dot marsden at ryerson dot ca<br /> * [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp; Archives<br /> <br /> Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. <br /> <br /> The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.<br /> <br /> The presentation will not only cover the technical aspects, but also the implementation and usability findings.<br /> <br /> == De-sucking the Library User Experience ==<br /> <br /> * Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu<br /> <br /> Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.<br /> <br /> The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.<br /> <br /> == Solr Testing Is Easy with Rspec-Solr Gem ==<br /> <br /> * Naomi Dushay, Stanford University, ndushay AT stanford DOT edu<br /> <br /> How do you know if <br /> <br /> * your idea for &quot;left anchoring&quot; searches actually works?<br /> * your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?<br /> * tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?<br /> * changes to your solrconfig file accomplish what you wanted without breaking anything else?<br /> <br /> Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:<br /> <br />  it &quot;unstemmed author name Zare should precede stemmed variants&quot; do<br />   resp = solr_response(author_search_args('Zare').merge({'fl'=&gt;'id,author_person_display', 'facet'=&gt;false}))<br />   resp.should include(&quot;author_person_display&quot; =&gt; /\bZare\W/).in_each_of_first(3).documents<br />   resp.should_not include(&quot;author_person_display&quot; =&gt; /Zaring/).in_each_of_first(20).documents<br />  end<br />   <br />  it &quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&quot; do<br />    resp = solr_resp_doc_ids_only({'q'=&gt;'Восемьсoт семьдесят один день'})<br />    resp.should include(&quot;9091779&quot;)<br />  end<br /> <br />  it &quot;q of 'String quartets Parts' and variants should be plausible &quot; do<br />    resp = solr_resp_doc_ids_only({'q'=&gt;'String quartets Parts'})<br />    resp.should have_at_least(2000).documents<br />    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'(String quartets Parts)'}))<br />    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&gt;'&quot;String quartets Parts&quot;'}))<br />  end<br /> <br /> it &quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&quot; do<br /> resp = solr_response({'q'=&gt;'三國誌', 'fl'=&gt;'id', 'facet'=&gt;false}) <br /> resp.should have_at_least(240).documents<br /> resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'三国志'})) <br /> end<br /> <br /> See<br />    http://rubydoc.info/github/sul-dlss/rspec-solr/frames<br />    https://github.com/sul-dlss/rspec-solr<br /> <br /> and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:<br />    https://github.com/sul-dlss/sw_index_tests<br /> <br /> <br /> <br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_talks_proposals&diff=27671 2012-10-29T17:23:14Z

<p>Ndushay: /* Solr Testing Is Easy with Rspec-Solr Gem */</p> <hr /> <div>Deadline for talk submission is ''Friday, November 2'' at 5pm PT.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br /> * tools (some cool new software, software library or integration platform)<br /> * specs (how to get the most out of some protocols, or proposals for new ones)<br /> * challenges (one or more big problems we should collectively address)<br /> <br /> The community will vote on proposals using the criteria of:<br /> * usefulness<br /> * newness<br /> * geekiness<br /> * uniqueness<br /> * awesomeness<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> == Talk Title ==<br /> <br /> * Speaker's name, affiliation, and email address<br /> * Second speaker's name, affiliation, email address, if applicable<br /> <br /> Abstract of no more than 500 words.<br /> &lt;/pre&gt;<br /> <br /> == Modernizing VuFind with Zend Framework 2 ==<br /> <br /> * Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu<br /> <br /> When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.<br /> <br /> == Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==<br /> <br /> * [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br /> <br /> Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby. <br /> Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]? <br /> It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.<br /> So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?<br /> This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.<br /> <br /> == Drupal 8 Preview — Symfony and Twig ==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.<br /> <br /> It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.<br /> <br /> Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.<br /> <br /> == Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==<br /> <br /> * Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu<br /> <br /> Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &quot;Let's digitize these together and make them one big awesome project to support public urban history&quot;? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of &quot;grand ideas crushed by technological limitations&quot; and &quot;projects on the right track&quot; to follow. <br /> <br /> == ResCarta Tools building a standard format for audio archiving, discovery and display ==<br /> <br /> * [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org<br /> <br /> The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit. <br /> <br /> Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.<br /> <br /> ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! <br /> <br /> You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old) <br /> <br /> == Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==<br /> <br /> * Michael Doran, University of Texas at Arlington, doran@uta.edu<br /> <br /> This presentation will use a seemingly simple data point, the &quot;format&quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. <br /> <br /> I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session. <br /> <br /> == Touch Kiosk 2: Piezoelectric Boogaloo ==<br /> <br /> * Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu<br /> <br /> At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.<br /> <br /> In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.<br /> <br /> I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.<br /> <br /> [1] http://journal.code4lib.org/articles/5832<br /> <br /> == Wayfinding in a Cloud: Location Service for libraries ==<br /> <br /> * Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi<br /> <br /> Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.<br /> <br /> The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.<br /> <br /> The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.<br /> <br /> == Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.<br /> * Automatically inventory a collection of documents or images to be uploaded<br /> * Generate a spreadsheet for metadata capture based on the inventory<br /> * Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested<br /> * Validate the contents of ingest folders prior to initiating the ingest to DSpace<br /> * Present users with a simple, web-based form to initiate the batch ingest process<br /> <br /> The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections. <br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == Quality Assurance Reports for DSpace Collections ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection<br /> <br /> These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.<br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==<br /> <br /> * Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca<br /> * Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca<br /> <br /> In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.<br /> <br /> See article: http://journal.code4lib.org/articles/7470<br /> <br /> == HTML5 Video Now! ==<br /> <br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> <br /> How to get started using HTML5 video right now, including gotchas, tips, tricks, and the future of video on the Web.<br /> <br /> == Hybrid Archival Collections Using Blacklight and Hydra ==<br /> <br /> * Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org<br /> <br /> At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.<br /> <br /> Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.<br /> <br /> == Making the Web Accessible through Solid Design ==<br /> <br /> * [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp; Archives<br /> <br /> In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.<br /> <br /> While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.<br /> <br /> == Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp; Much More ==<br /> <br /> * Steven Marsden, Ryerson University Library &amp; Archives, steven dot marsden at ryerson dot ca<br /> * [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp; Archives<br /> <br /> Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. <br /> <br /> The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.<br /> <br /> The presentation will not only cover the technical aspects, but also the implementation and usability findings.<br /> <br /> == De-sucking the Library User Experience ==<br /> <br /> * Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu<br /> <br /> Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.<br /> <br /> The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.<br /> <br /> == Solr Testing Is Easy with Rspec-Solr Gem ==<br /> <br /> * Naomi Dushay, Stanford University, ndushay AT stanford DOT edu<br /> <br /> How do you know if <br /> <br /> * your idea for &quot;left anchoring&quot; searches actually works?<br /> * your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?<br /> * tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?<br /> * changes to your solrconfig file accomplish what you wanted without breaking anything else?<br /> <br /> Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:<br /> <br />   it &quot;unstemmed author name Zare should precede stemmed variants&quot; do<br />     resp = solr_response(author_search_args('Zare').merge({'fl'=&gt;'id,author_person_display', 'facet'=&gt;false}))<br />     resp.should include(&quot;author_person_display&quot; =&gt; /\bZare\W/).in_each_of_first(3).documents<br />     resp.should_not include(&quot;author_person_display&quot; =&gt; /Zaring/).in_each_of_first(20).documents<br />   end<br /> <br />   it &quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&quot; do<br />     resp = solr_resp_doc_ids_only({'q'=&gt;'Восемьсoт семьдесят один день'})<br />     resp.should include(&quot;9091779&quot;)<br />   end<br /> <br />   it &quot;q of 'String quartets Parts' and variants should be plausible &quot; do<br />     resp = solr_resp_doc_ids_only({'q'=&gt;'String quartets Parts'})<br />     resp.should have_at_least(2000).documents<br />     resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'(String quartets Parts)'}))<br />     resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&gt;'&quot;String quartets Parts&quot;'}))<br />   end<br /> <br /> it &quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&quot; do<br /> resp = solr_response({'q'=&gt;'三國誌', 'fl'=&gt;'id', 'facet'=&gt;false}) <br /> resp.should have_at_least(240).documents<br /> resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'三国志'})) <br /> end<br /> <br /> See<br />    http://rubydoc.info/github/sul-dlss/rspec-solr/frames<br />    https://github.com/sul-dlss/rspec-solr<br /> <br /> and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:<br />    https://github.com/sul-dlss/sw_index_tests<br /> <br /> <br /> <br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=2013_talks_proposals&diff=27670 2012-10-29T17:21:55Z

<p>Ndushay: added a talk proposal.</p> <hr /> <div>Deadline for talk submission is ''Friday, November 2'' at 5pm PT.<br /> <br /> Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br /> * tools (some cool new software, software library or integration platform)<br /> * specs (how to get the most out of some protocols, or proposals for new ones)<br /> * challenges (one or more big problems we should collectively address)<br /> <br /> The community will vote on proposals using the criteria of:<br /> * usefulness<br /> * newness<br /> * geekiness<br /> * uniqueness<br /> * awesomeness<br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> == Talk Title ==<br /> <br /> * Speaker's name, affiliation, and email address<br /> * Second speaker's name, affiliation, email address, if applicable<br /> <br /> Abstract of no more than 500 words.<br /> &lt;/pre&gt;<br /> <br /> == Modernizing VuFind with Zend Framework 2 ==<br /> <br /> * Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu<br /> <br /> When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.<br /> <br /> == Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==<br /> <br /> * [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br /> <br /> Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby. <br /> Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]? <br /> It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.<br /> So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?<br /> This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.<br /> <br /> == Drupal 8 Preview — Symfony and Twig ==<br /> <br /> * [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br /> <br /> Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.<br /> <br /> It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.<br /> <br /> Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.<br /> <br /> == Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==<br /> <br /> * Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu<br /> <br /> Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &quot;Let's digitize these together and make them one big awesome project to support public urban history&quot;? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of &quot;grand ideas crushed by technological limitations&quot; and &quot;projects on the right track&quot; to follow. <br /> <br /> == ResCarta Tools building a standard format for audio archiving, discovery and display ==<br /> <br /> * [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org<br /> <br /> The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit. <br /> <br /> Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.<br /> <br /> ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! <br /> <br /> You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old) <br /> <br /> == Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==<br /> <br /> * Michael Doran, University of Texas at Arlington, doran@uta.edu<br /> <br /> This presentation will use a seemingly simple data point, the &quot;format&quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. <br /> <br /> I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session. <br /> <br /> == Touch Kiosk 2: Piezoelectric Boogaloo ==<br /> <br /> * Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu<br /> <br /> At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.<br /> <br /> In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.<br /> <br /> I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.<br /> <br /> [1] http://journal.code4lib.org/articles/5832<br /> <br /> == Wayfinding in a Cloud: Location Service for libraries ==<br /> <br /> * Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi<br /> <br /> Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.<br /> <br /> The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.<br /> <br /> The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.<br /> <br /> == Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.<br /> * Automatically inventory a collection of documents or images to be uploaded<br /> * Generate a spreadsheet for metadata capture based on the inventory<br /> * Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested<br /> * Validate the contents of ingest folders prior to initiating the ingest to DSpace<br /> * Present users with a simple, web-based form to initiate the batch ingest process<br /> <br /> The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections. <br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == Quality Assurance Reports for DSpace Collections ==<br /> <br /> * Terry Brady, Georgetown University, twb27@georgetown.edu<br /> <br /> The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection<br /> <br /> These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.<br /> <br /> In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.<br /> <br /> == A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==<br /> <br /> * Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca<br /> * Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca<br /> <br /> In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.<br /> <br /> See article: http://journal.code4lib.org/articles/7470<br /> <br /> == HTML5 Video Now! ==<br /> <br /> * Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br /> <br /> How to get started using HTML5 video right now, including gotchas, tips, tricks, and the future of video on the Web.<br /> <br /> == Hybrid Archival Collections Using Blacklight and Hydra ==<br /> <br /> * Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org<br /> <br /> At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.<br /> <br /> Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.<br /> <br /> == Making the Web Accessible through Solid Design ==<br /> <br /> * [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp; Archives<br /> <br /> In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.<br /> <br /> While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.<br /> <br /> == Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp; Much More ==<br /> <br /> * Steven Marsden, Ryerson University Library &amp; Archives, steven dot marsden at ryerson dot ca<br /> * [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp; Archives<br /> <br /> Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. <br /> <br /> The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.<br /> <br /> The presentation will not only cover the technical aspects, but also the implementation and usability findings.<br /> <br /> == De-sucking the Library User Experience ==<br /> <br /> * Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu<br /> <br /> Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.<br /> <br /> The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.<br /> <br /> == Solr Testing Is Easy with Rspec-Solr Gem ==<br /> <br /> * Naomi Dushay, Stanford University, ndushay AT stanford DOT edu<br /> <br /> How do you know if <br /> <br /> * your idea for &quot;left anchoring&quot; searches actually works?<br /> * your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?<br /> * tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?<br /> * changes to your solrconfig file accomplish what you wanted without breaking anything else?<br /> <br /> Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:<br /> <br />   it &quot;unstemmed author name Zare should precede stemmed variants&quot; do<br />     resp = solr_response(author_search_args('Zare').merge({'fl'=&gt;'id,author_person_display', 'facet'=&gt;false}))<br />     resp.should include(&quot;author_person_display&quot; =&gt; /\bZare\W/).in_each_of_first(3).documents<br />     resp.should_not include(&quot;author_person_display&quot; =&gt; /Zaring/).in_each_of_first(20).documents<br />   end<br /> <br />   it &quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&quot; do<br />     resp = solr_resp_doc_ids_only({'q'=&gt;'Восемьсoт семьдесят один день'})<br />     resp.should include(&quot;9091779&quot;)<br />   end<br /> <br />   it &quot;q of 'String quartets Parts' and variants should be plausible &quot; do<br />     resp = solr_resp_doc_ids_only({'q'=&gt;'String quartets Parts'})<br />     resp.should have_at_least(2000).documents<br />     resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'(String quartets Parts)'}))<br />     resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&gt;'&quot;String quartets Parts&quot;'}))<br />   end<br /> <br /> it &quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&quot; do<br /> resp = solr_response({'q'=&gt;'三國誌', 'fl'=&gt;'id', 'facet'=&gt;false}) <br /> resp.should have_at_least(240).documents<br /> resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&gt;'三国志'})) <br /> end<br /> <br /> See<br />    http://rubydoc.info/github/sul-dlss/rspec-solr/frames<br />    https://github.com/sul-dlss/rspec-solr<br /> <br /> and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:<br />    https://github.com/sul-dlss/sw_index_tests<br /> <br /> <br /> <br /> [[Category:Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11395 2012-02-10T18:51:15Z

<p>Ndushay: /* Food */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary - as long as notes go on wiki or someplace<br /> # explicitly state that presentation with (most/least) votes will be on day 3, since so many people plan to leave early -- could affect their planning.<br /> # Breakout sessions could be proposed and voted on prior to conference -- ad hoc breakouts didn't provide much interest to some of us.<br /> <br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> # Maybe some evening groups for music, shows, etc.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> ## (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> # Automated Testing<br /> # Two words: Soft pretzels.<br /> <br /> ==Registration==<br /> * Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> * Choose talks before registration<br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> * Have one projection screen above or beside speaker so possible to view speaker and slides at the same time.<br /> * attendee list handouts should have name, institution, irc handle ... (preferably a sorted mapping from irc handle -&gt; names, a sort by firstname, and maybe a sort by last name)<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11394 2012-02-10T18:50:20Z

<p>Ndushay: /* Schedule */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary - as long as notes go on wiki or someplace<br /> # explicitly state that presentation with (most/least) votes will be on day 3, since so many people plan to leave early -- could affect their planning.<br /> # Breakout sessions could be proposed and voted on prior to conference -- ad hoc breakouts didn't provide much interest to some of us.<br /> <br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> # Maybe some evening groups for music, shows, etc.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> * Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> * Choose talks before registration<br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> * Have one projection screen above or beside speaker so possible to view speaker and slides at the same time.<br /> * attendee list handouts should have name, institution, irc handle ... (preferably a sorted mapping from irc handle -&gt; names, a sort by firstname, and maybe a sort by last name)<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11383 2012-02-09T19:28:16Z

<p>Ndushay: /* Other ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> # explicitly state that presentation with (most/least) votes will be on day 3, since so many people plan to leave early -- could affect their planning.<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> # Maybe some evening groups for music, shows, etc.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> * Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> * Choose talks before registration<br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> * Have one projection screen above or beside speaker so possible to view speaker and slides at the same time.<br /> * attendee list handouts should have name, institution, irc handle ... (preferably a sorted mapping from irc handle -&gt; names, a sort by firstname, and maybe a sort by last name)<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11380 2012-02-09T19:11:35Z

<p>Ndushay: /* Code4Lib 2013 ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> # explicitly state that presentation with (most/least) votes will be on day 3, since so many people plan to leave early -- could affect their planning.<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> # Maybe some evening groups for music, shows, etc.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> * Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> * Choose talks before registration<br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11377 2012-02-09T19:05:51Z

<p>Ndushay: /* Social Schedule */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> # Maybe some evening groups for music, shows, etc.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11376 2012-02-09T19:04:55Z

<p>Ndushay: /* Code4Lib 2013 ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> # Have a reception in a museum or library, if possible<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11375 2012-02-09T19:02:29Z

<p>Ndushay: /* Other ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> * sign on podium &quot;repeat the question&quot;<br /> * mc tells each presenter how to use the mic effectively<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11372 2012-02-09T17:46:20Z

<p>Ndushay: /* Other ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> * Announce scholarship winners the first day so that folks have a chance to meet them<br /> * microphones for audience<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11315 2012-02-08T19:15:14Z

<p>Ndushay: /* Other ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> * Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11242 2012-02-08T00:19:38Z

<p>Ndushay: /* Schedule */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> ===Social Schedule===<br /> # Newcomer welcome on first night?<br /> # Beer party needs a big enough space<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11239 2012-02-08T00:18:19Z

<p>Ndushay: </p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> # Beer party needs a big enough space.<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11237 2012-02-08T00:17:43Z

<p>Ndushay: /* T-shirts */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> # Beer party needs a big enough space.<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> ** How about going blind from some t-shirt submissions? ;-)<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11235 2012-02-08T00:17:06Z

<p>Ndushay: /* Food */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians / Vegans<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> # Beer party needs a big enough space.<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11234 2012-02-08T00:16:41Z

<p>Ndushay: /* Code4Lib 2013 ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> # no breakout reports - many feel they are unnecessary<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> # Two words: Soft pretzels. <br /> # Beer party needs a big enough space.<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> ==Registration==<br /> Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated<br /> <br /> <br /> ==T-shirts==<br /> * Men's and ladies sizes -- can it be done?<br /> * 100% cotton is worth it.<br /> * How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.<br /> <br /> ==Suggestions from dchuds talk==<br /> <br /> * less complacency from overall committee--less burden on local org committee <br /> * Advisory committee - made up of representatives from past hosts<br /> * Programming committee - don't have voting on talks<br /> * do work in the open<br /> * build on experience from past conferences<br /> * code4lib multicore<br /> * multi-track conference<br /> * support 500 people<br /> * make it more like PyCon<br /> <br /> ==Other ideas==<br /> * more regional c4l (but drop the &quot;regional&quot; suffix) <br /> * keep voting on programming!!!<br /> <br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11078 2012-02-07T17:04:24Z

<p>Ndushay: /* Code4Lib 2013 ideas */</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> # Automated Testing<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11076 2012-02-07T17:02:26Z

<p>Ndushay: </p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free<br /> # Avoid snow and bitter cold!<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2013&diff=11074 2012-02-07T17:01:47Z

<p>Ndushay: New page: =Code4Lib 2013 ideas= ===Schedule=== # Keep Super Bowl Sunday free ==Food== # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people ...</p> <hr /> <div>=Code4Lib 2013 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free <br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> [[Category: Code4Lib2013]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11068 2012-02-07T16:54:15Z

<p>Ndushay: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11067 2012-02-07T16:52:38Z

<p>Ndushay: /* Conference */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11066 2012-02-07T16:52:20Z

<p>Ndushay: /* Conference */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11065 2012-02-07T16:51:49Z

<p>Ndushay: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11064 2012-02-07T16:50:03Z

<p>Ndushay: /* Suggested Timeline */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11063 2012-02-07T16:49:06Z

<p>Ndushay: /* Video */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11062 2012-02-07T16:48:50Z

<p>Ndushay: /* Conference */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> == Video ==<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11061 2012-02-07T16:48:30Z

<p>Ndushay: /* PreConf */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> == Conference ==<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> == Video ==<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=11060 2012-02-07T16:47:52Z

<p>Ndushay: /* At the Conference */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> <br /> (Add more info for the program committee here!)<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to ask if they need anything, arrange airport pickup, etc<br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ==PreConf==<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> == Conference ==<br /> # power <br /> # super duper high bandwidth network<br /> # ports allow for IRC, VPN<br /> <br /> == Video ==<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Ask Anything===<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> <br /> ===Calls for Hosting===<br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013:</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2012&diff=11059 2012-02-07T16:46:05Z

<p>Ndushay: /* PreConf */</p> <hr /> <div>=Code4Lib 2012 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free (February 5, 2012)<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> [[Category: Code4Lib2012]]</div>

Ndushay https://wiki.code4lib.org/index.php?title=Ideas_for_2012&diff=11058 2012-02-07T16:43:15Z

<p>Ndushay: /* Code4Lib 2012 ideas */</p> <hr /> <div>=Code4Lib 2012 ideas=<br /> <br /> ===Schedule===<br /> # Keep Super Bowl Sunday free (February 5, 2012)<br /> <br /> ==Food==<br /> <br /> # If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)<br /> # Is it possible to get a hot breakfast with/instead of continental?<br /> # Consider Vegetarians<br /> # Decent lunch menu - not taco or spaghetti :-)<br /> <br /> (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)<br /> <br /> [[Category: Code4Lib2012]]<br /> <br /> ==PreConf==<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10988 2012-02-06T18:07:26Z

<p>Ndushay: /* Potential projects */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - linking data available about books that are available online in [http://everybodyslibraries.com/ John Ockerbloom]'s [http://onlinebooks.library.upenn.edu/aboutolbp.html Online Books Website] to [http://books.google.com Google Books]<br /> * dchud - social network for people and their bibliographic obsessions with caching piece<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.xml Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> * caching linked data for performance (Dan Chudnov)<br /> * use &quot;common vocab&quot; in something like http://jobs.code4lib.org/ (Corey Harper) - the common vocabs from linked data make catalogers jobs easier<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> ** http://www.w3.org/1999/02/22-rdf-syntax-ns#type<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasauris.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld<br /> * https://subj3ct.com/</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10986 2012-02-06T18:05:32Z

<p>Ndushay: /* Resources */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - linking data available about books that are available online in [http://everybodyslibraries.com/ John Ockerbloom]'s [http://onlinebooks.library.upenn.edu/aboutolbp.html Online Books Website] to [http://books.google.com Google Books]<br /> * dchud - personal bibliographic wotsit<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.xml Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> * caching linked data for performance (Dan Chudnov)<br /> * use &quot;common vocab&quot; in something like http://jobs.code4lib.org/ (Corey Harper)<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> ** http://www.w3.org/1999/02/22-rdf-syntax-ns#type<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasauris.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld<br /> * https://subj3ct.com/</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10983 2012-02-06T18:02:02Z

<p>Ndushay: /* Potential projects */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - linking data available about books that are available online in [http://onlinebooks.library.upenn.edu/aboutolbp.html Online Books Page] to [http://books.google.com Google Books]<br /> * dchud - personal bibliographic wotsit<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.xml Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> * caching linked data for performance (Dan Chudnov)<br /> * use &quot;common vocab&quot; in something like http://jobs.code4lib.org/ (Corey Harper)<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> ** http://www.w3.org/1999/02/22-rdf-syntax-ns#type<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasauris.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10982 2012-02-06T18:00:05Z

<p>Ndushay: /* Potential projects */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - linking data available about books that are available online in [http://onlinebooks.library.upenn.edu/aboutolbp.html Online Books Page] to [http://books.google.com Google Books]<br /> * dchud - personal bibliographic wotsit<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.xml Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> * caching linked data for performance (Dan Chudnov)<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> ** http://www.w3.org/1999/02/22-rdf-syntax-ns#type<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasauris.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10973 2012-02-06T17:50:35Z

<p>Ndushay: /* Resources */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - unglue.it<br /> * dchud - personal bibliographic wotsit<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.html Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> ** http://www.w3.org/1999/02/22-rdf-syntax-ns#type<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasaurius.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld</div>

Ndushay https://wiki.code4lib.org/index.php?title=2012_Linkfest_Preconference&diff=10971 2012-02-06T17:49:08Z

<p>Ndushay: /* Resources */</p> <hr /> <div>== Description == <br /> <br /> We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br /> <br /> If you need an &quot;intro to linked data&quot; we can prep a good list of readings/talks to review before you come. But please come ready to link!<br /> Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br /> <br /> == Potential projects ==<br /> <br /> * charper - working with [http://www.tagasauris.com/ tagasauris]<br /> * tim shearer - reconciling against geonames<br /> * edsu - unglue.it<br /> * dchud - personal bibliographic wotsit<br /> * helrond - reconciling lists of names from EAD to amplify existing description ([http://dlib.nyu.edu/findingaids/html/tamwag/dw_photos.html Daily Worker - Communist Party of USA photos] - finding aid is big; be patient...)<br /> * declan<br /> * jpstroop - linking data, adding URIs etc to EAD<br /> * jaron (@ronallo) Jason Ronallo - making microdata more like linked data<br /> <br /> == Success stories (or at least interesting stories) ==<br /> <br /> * [http://jobs.code4lib.org jobs.code4lib.org] use of [http://www.freebase.com/docs/suggest Freebase Suggest] enables a view like [http://jobs.code4lib.org/jobs/ruby/ all Ruby jobs]<br /> * [http://chroniclingamerica.loc.gov/ Chronicling America] use of [http://sitemaps.org sitemaps] and delivery of OCR data, for example take a look at the source code of [http://chroniclingamerica.loc.gov/lccn/sn83025121/1912-02-06/ed-1/seq-1/ this newspaper page resource]<br /> * [https://developers.facebook.com/docs/reference/api/ Facebook Graph API] JSON representations of resources w/ typed links to other JSON representations of Resources = Linked Data<br /> <br /> == Resources == <br /> <br /> * [http://www.w3.org/RDF/ W3C RDF Tools page]<br /> * DLIB article; see section on Linking Authorities if that interests you: http://www.dlib.org/dlib/november10/byrne/11byrne.html<br /> * [http://www.diglib.org/forums/2011forum/schedule/linked-data-hands-on-how-to/ DLF Fall Forum 2011 Linked Data Hands-on How-to] includes tutorials and sample data sets<br /> * [http://freeyourmetadata.org/ Free Your Metadata]<br /> * [http://www.tagasaurius.com/ Tagasaurius]<br /> * http://thedatahub.org/group/lld</div>

Ndushay