Proposals will be accepted through December 6th, 2013.
===Note===
Registration for a pre-conference will require a small fee ''due at the time of registration.'' Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock."
Please fill out your proposal in the following format. If you are interested in attending a proposed pre-conference add your name to the list for that proposal.
----
===Drupal4lib Sub-con Barcamp===
=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu* TA: Bess Sadler, Stanford University, bess@stanford.edu
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
#Megan Kudzia
#Bret Davidson
#Coral Sheldon-Hess
===Blacklight Hackfest===
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
1. Shaun Ellis
===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
1. Ayla Stein
2. Heidi Dowding
===Managing Projects: Or I'm in charge, now what?===
'''Full-Day'''
Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu
This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good)
'''Interested in Attending'''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''
Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.
The schedule may include the following:
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?
''Interested in attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
#Bret Davidson
===CLLAM @ code4lib===
'''(Computational Linguistics for Libraries, Archives and Museums)'''
'''Full Day'''
Contacts:
* Douglas W. Oard (primary), oard (at) umd.edu
* Corey Harper, corey (dot) harper (at) nyu.edu
* Robert Sanderson, azaroth42 (at) gmail.com
* Robert Warren, rwarren (at) math.carleton.ca
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers.
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.
''Interested in attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Devon Smith
# Kevin S. Clarke
=== GeoHydra: Managing geospatial content ===
'''Half-day [Afternoon]'''
* Contact: Darren Hardy, Stanford University, drh@stanford.edu
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,
etc., all of which you want to integrate into your digital repository? In this
workshop, we will discuss how Hydra can provide discovery, delivery, and
management services for geospatial assets, as well as solicit questions about
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:
* What are the types of geospatial data?
* How to dive into Hydra?
* How to model geospatial holdings with Hydra?
* How to discover and view geospatial data?
* How to build a geospatial data infrastructure?
* What are common approaches and problems?
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
===Technology, Librarianship, and Gender: Moving the conversation forward===
'''Full Day'''
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]
'''Description'''
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?
Lots of tough questions.
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
=====All Day=====
1. Kate Kosturski
2. Valerie Aurora
=====Morning=====
1. Shaun Ellis
=====Afternoon=====
1. Ayla Stein
2. Heidi Dowding
3. Coral Sheldon-Hess
----
===FileAnalyzer: Rapid Development of File Manipulation Tasks===
'''"Half-Day" [morning]'''
* Contact Terry Brady, twb27@georgetown.edu
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:
* validating digitized and reformatted files
* validating vendor statistics for counter compliance
* preparing collections of digital files for archiving and ingest
* manipulating ILS import and export files
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.
The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.
''Session Overview''
* Overview of the application
* Running sample file tests/transformations through the application
* Compiling and building the application
* Coding a custom file processing task
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
----
===Collecting social media data with Social Feed Manager===
'''Half-Day [Morning]'''
Contacts:
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu
Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
----
[[:Category:Code4Lib2014]]
