https://wiki.code4lib.org/api.php?action=feedcontributions&user=Ajconsta&feedformat=atomCode4Lib - User contributions [en]2024-03-28T19:07:30ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&diff=427902015 Lightning Talks2015-02-11T21:14:05Z<p>Ajconsta: edit to reflect reality</p>
<hr />
<div><br />
==Lightning Talks==<br />
<big>'''Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.'''</big><br />
<br />
==Tuesday 14:30 PM to 15:30 PM==<br />
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee<br />
# ResCarta Recap<br />
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre<br />
# Vufind & Worldcat Discovery API - Karen Coombs<br />
# [http://ronallo.com/presentations/ Video Accessibility on the Web] - Jason Ronallo<br />
# [https://docs.google.com/presentation/d/11vBKfYbGzp5_gyksPqK1WKLvMVO_aMk03x2PvK1p_u8/view?usp=sharing ILS and Payment Systems] - Josh Weisman<br />
# Fedora 4 Migration - Adam Wead<br />
# [https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath] - Chris Beer<br />
# [https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data] - Darren Hardy<br />
# [http://matienzo.org/c4l15-lightning-talk Bread (How Baking Bread Made Me a Better Programmer)] - Mx Matienzo<br />
<br />
==Wednesday 11:00 AM to 12:00 PM==<br />
# [http://bit.ly/rightspres rights metadata] esmé cowles<br />
# [https://speakerdeck.com/nabeta/2014-2015-activities-of-code4lib-japan 2014-2015 Activities around code4lib Japan] - Kosuke Tanabe<br />
# [https://docs.google.com/presentation/d/1oJtzHWcIie-vLCpU-c_T6GaUCkWrPp0E9QDYqXiiH3M/edit?usp=sharing Arduino as a Learning Platform] - Dominic Bordelon<br />
# [http://ablwr.github.io/c4l_preforma/#/ PreForma (Preservation Formats Project)] - Ashley Blewer<br />
# PBEBUCore - Casey E. Davis<br />
# RDF for relational database developers - Hector Correa <br />
# [http://intro2libsys.info/code4lib-2015 Building a BIBFRAME catalog] - Jeremy Nelson<br />
# [http://www.mukurtu.org Mukurtu CMS] - Alex Merrill<br />
# Drupal, git, and sanity - Charlie M.<br />
# How do we improve as developers? - Trey Terrell<br />
<br />
==Thursday 9:30 AM to 10:15 AM ==<br />
<br />
# [https://github.com/OpenGeoMetadata/metadatarepository OpenGeoMetadata] : Let's share our geo metadata<br />
# IIIF Image Drupal module<br />
# Clustering moving image works - Kelley McGrath<br />
# Islandora Fedora 4 proof of concept - Danny Lamb<br />
# Measure the future - Jason Griffey<br />
# Low hanging fruit of accessibility - Kate Deibel<br />
# Planning for the data schlep - Adam Constabaris <br />
# Archiving the silenced - Natasha Nunn<br />
# The Great Migration: Fedora 4 - Andrew Woods<br />
<br />
[[Category:Code4Lib2015]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&diff=427892015 Lightning Talks2015-02-11T21:13:25Z<p>Ajconsta: moved around lightning talks to reflect reality</p>
<hr />
<div><br />
==Lightning Talks==<br />
<big>'''Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.'''</big><br />
<br />
==Tuesday 14:30 PM to 15:30 PM==<br />
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee<br />
# ResCarta Recap<br />
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre<br />
# Vufind & Worldcat Discovery API - Karen Coombs<br />
# [http://ronallo.com/presentations/ Video Accessibility on the Web] - Jason Ronallo<br />
# [https://docs.google.com/presentation/d/11vBKfYbGzp5_gyksPqK1WKLvMVO_aMk03x2PvK1p_u8/view?usp=sharing ILS and Payment Systems] - Josh Weisman<br />
# Fedora 4 Migration - Adam Wead<br />
# [https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath] - Chris Beer<br />
# [https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data] - Darren Hardy<br />
# [http://matienzo.org/c4l15-lightning-talk Bread (How Baking Bread Made Me a Better Programmer)] - Mx Matienzo<br />
<br />
==Wednesday 11:00 AM to 12:00 PM==<br />
# [http://bit.ly/rightspres rights metadata] esmé cowles<br />
# [https://speakerdeck.com/nabeta/2014-2015-activities-of-code4lib-japan 2014-2015 Activities around code4lib Japan] - Kosuke Tanabe<br />
# [https://docs.google.com/presentation/d/1oJtzHWcIie-vLCpU-c_T6GaUCkWrPp0E9QDYqXiiH3M/edit?usp=sharing Arduino as a Learning Platform] - Dominic Bordelon<br />
# [http://ablwr.github.io/c4l_preforma/#/ PreForma (Preservation Formats Project)] - Ashley Blewer<br />
# PBEBUCore - Casey E. Davis<br />
# RDF for relational database developers - Hector Correa <br />
# [http://intro2libsys.info/code4lib-2015 Building a BIBFRAME catalog] - Jeremy Nelson<br />
# [http://www.mukurtu.org Mukurtu CMS] - Alex Merrill<br />
# Planning for the data schlep - Adam Constaburis<br />
# How do we improve as developers? - Trey Terrell<br />
<br />
==Thursday 9:30 AM to 10:15 AM ==<br />
<br />
# [https://github.com/OpenGeoMetadata/metadatarepository OpenGeoMetadata] : Let's share our geo metadata<br />
# IIIF Image Drupal module<br />
# Clustering moving image works - Kelley McGrath<br />
# Islandora Fedora 4 proof of concept - Danny Lamb<br />
# Measure the future - Jason Griffey<br />
# Low hanging fruit of accessibility - Kate Deibel<br />
# Planning for the data schlep - Adam Constabaris <br />
# Archiving the silenced - Natasha Nunn<br />
# The Great Migration: Fedora 4 - Andrew Woods<br />
<br />
[[Category:Code4Lib2015]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=410242014 Lessons Learned2014-03-28T18:36:20Z<p>Ajconsta: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
* When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br />
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br />
* Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
* Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
* When putting out a call for any graphics, ensure that the formats submitted are usable in production (e.g. vector formats).<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
* Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Diebold-o-Tron)<br />
<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br />
* Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br />
<br />
* Communicate early and often with organizers and have a plan for '''getting a solid schedule''' as early as possible (this can help some organizers provide the needed justification to their institutions for travel support). Consider this in light of your winnowing process.<br />
* (Also applies to the A/V section) find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, and wifi, power availability, etc. up front.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br />
* A Google Calendar worked well this year in establishing all deadlines across all committees.<br />
* A regularly occurring meeting of some planning group helps keep things moving.<br />
* See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br />
<br />
'''IRC'''<br />
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br />
*Start the process to get the freenode limit raised a month before to plan for any kinks!<br />
*Announce channel logging a month or more ahead of time <br />
<br />
'''Scholarships'''<br />
<br />
* forthcoming!<br />
<br />
'''Keynotes'''<br />
* It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br />
<br />
'''Ideas'''<br />
* Lanyards for whether it is OK to take photographs<br />
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br />
* Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br />
** Another possibility could be to have the room next to the hospitality room be reserved for a "suite steward" or "host" volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br />
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br />
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br />
* Consider precombining lightning talks into a single slide deck to keep the flow going.<br />
* Consider live closed captioning software for talks and streaming<br />
* IRC channel shown on screens when no presenter is up<br />
* Consider switches at the tables<br />
* Add a Code4Lib logo to the podium<br />
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=410192014 Lessons Learned2014-03-28T18:21:00Z<p>Ajconsta: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
* When putting out a call for any graphics, ensure that the formats submitted are usable in production.<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Debold-o-Tron)<br />
<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br />
<br />
* Communicate early and often with organizers and have a plan for *having a solid plan* as early as possible (this can help some organizers provide the needed justification to their instituitions for travel support).<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
* While you're at that, find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, *and* wifi and power availability up front.<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br />
'''IRC'''<br />
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br />
*Start the process to get the freenode limit raised a month before to plan for any kinks!<br />
*Announce channel logging a month or more ahead of time <br />
<br />
'''Scholarships'''<br />
<br />
* forthcoming!<br />
<br />
'''Ideas'''<br />
* Lanyards for whether it is OK to take photographs<br />
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br />
* Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br />
** Another possibility could be to have the room next to the hospitality room be reserved for a "suite steward" or "host" volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br />
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br />
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br />
* Consider precombining lightning talks into a single slide deck to keep the flow going.<br />
* Consider live closed captioning software for talks and streaming<br />
* IRC channel shown on screens when no presenter is up<br />
* Consider switches at the tables<br />
* Add a Code4Lib logo to the podium<br />
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_During_the_Conference_Volunteers&diff=405662014 During the Conference Volunteers2014-03-07T18:40:14Z<p>Ajconsta: </p>
<hr />
<div>code4lib 2014 During the Conference Volunteers<br />
<br />
== Hospitality Suite Committee ==<br />
<br />
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.<br />
<br />
<br />
== Welcome Wagon Committee ==<br />
<br />
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.<br />
<br />
* Becky Yoose (b.yoose at google)<br />
<br />
== Social Networking ==<br />
Responsible for non-IRC social networking presence.<br />
<br />
For 2014, we might assign 1-2 person(s) to take questions for sessions (assuming there's time) via Twitter/IRC. Just a thought.<br />
<br />
* Coral Sheldon-Hess (@web_kunoichi on Twitter, coral on IRC) - let me know what you need<br />
<br />
== IRC Evangelists ==<br />
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.<br />
<br />
== IRC Access ==<br />
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.<br />
<br />
One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "code4lib" as the "Channel".<br />
<br />
==Registration Desk Volunteers==<br />
<br />
CONCENTRA will be working at the registration desk. We are looking for possibly one person to be a code4lib presence at the desk on Tuesday morning.<br />
<br />
Tuesday 8-9 am<br />
<br />
Adam Constabaris (first dot last with the cases on the down-low at gmail)<br />
<br />
==MCs==<br />
<br />
Tuesday AM<br />
<br />
<br />
Tuesday PM<br />
<br />
* Dre, destroyer of cookies, doesn't look as good in a hat as Becky.<br />
<br />
<br />
Wednesday AM<br />
<br />
*Becky, destroyer of last names, singer of badly adapted show tunes <br />
<br />
<br />
Wednesday PM<br />
*Rosalyn, destroyer of fun, not as entertaining as Becky<br />
<br />
<br />
Thursday AM<br />
* Cynthia, destroyer of jokes, babbler of the universe<br />
<br />
== Session Timer Volunteers ==<br />
<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
'''Schedule for Session Timers'''<br />
<br />
Tuesday AM<br />
* Francis Kayiwa<br />
<br />
<br />
Tuesday PM<br />
* Peter Murray<br />
<br />
Wednesday AM<br />
<br />
<br />
Wednesday PM<br />
<br />
<br />
Thursday AM<br />
<br />
== Raffles ==<br />
<br />
== Whatever Else Needs to be Done ==<br />
<br />
* Roy Tennant, royt in channel, text to 707-287-5580<br />
<br />
[[Category: Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=402502014 preconference proposals2014-01-15T17:31:28Z<p>Ajconsta: /* FileAnalyzer: Rapid Development of File Manipulation Tasks */</p>
<hr />
<div>= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. <br />
<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".<br />
<br />
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." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
=Code4Lib 2014 Pre-Conference Proposals=<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
<br />
* Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
* Kevin Reiss<br />
* Charlie Morris (NCSU) - glad to see this again this year!<br />
* Paula Gray-Overtoom<br />
* Laurie Lee Moses<br />
<br />
=====Afternoon=====<br />
<br />
&nbsp;<br />
<br />
----<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
<ol><br />
<li>Adam Constabaris<br />
<li>Ray Schwartz<br />
<li>Jason Stirnaman<br />
<li>Joshua Gomez<br />
<li>Sam Kome<br />
<li>Mike Beccaria<br />
<li>Angela Zoss<br />
<li>A. Soroka<br />
<li> Matt Zumwalt<br />
</ol><br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
# Bret Davidson<br />
# Coral Sheldon-Hess<br />
# Cory Lown<br />
# Emily Daly<br />
# Angela Zoss<br />
# Sean Aery<br />
# Francis Kayiwa<br />
# Heidi Frank<br />
----<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
# Shaun Ellis<br />
# Kevin Reiss<br />
# Megan Kudzia<br />
# Erik Hatcher<br />
# Emily Daly<br />
# Laurie Lee Moses<br />
# Francis Kayiwa<br />
<br />
----<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<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! 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 Blacklight and Hydra.<br />
<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 />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Caitlin Christian-Lamb<br />
<br />
4. Scott Bacon<br />
<br />
5. [[User:RileyChilds | Riley Childs]]<br />
<br />
6. Carolina Garcia<br />
<br />
----<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<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 />
# Robin Dean<br />
# Erin White<br />
# Andrew Darby<br />
# Sam Kome<br />
# Ryan Scherle<br />
# Will Shaw<br />
# Liz Milewicz<br />
# Cynthia "Arty" Ng<br />
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)<br />
# Ranti Junus<br />
# Bohyun Kim (Afternoon)<br />
<br />
----<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* 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?<br />
* 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?<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 />
#Bret Davidson<br />
#Mike Graves<br />
#Ray Schwartz<br />
#Jason Stirnaman<br />
#Julia Bauder<br />
#Linda Ballinger<br />
#Scott Hanrath<br />
#Caitlin Christian-Lamb<br />
#Ian Walls<br />
#Scott Bacon <br />
#mx matienzo<br />
#Chris Sharp<br />
<br />
----<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
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. <br />
<br />
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.<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 />
# Devon Smith<br />
# Kevin S. Clarke<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Carolina Garcia<br />
# Tom Burton-West<br />
# Dan Scott<br />
# Devin Higgins<br />
----<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
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:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<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 />
# Esmé Cowles<br />
----<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
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?<br />
<br />
Lots of tough questions.<br />
<br />
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.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
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<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 />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming (I'd be good with a half day too)<br />
<br />
4. mx matienzo (likewise ok w/ half day)<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
3. Bohyun Kim<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
<br />
4. Cory Lown<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<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 />
# Michael Doran<br />
----<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
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:<br />
* 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.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* 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)<br />
<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 />
# Declan Fleming<br />
# Esmé Cowles<br />
# Jason Stirnaman<br />
# Ray Schwartz<br />
# Liz Milewicz<br />
# Ranti Junus<br />
<br />
----<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<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 />
# Sam Kome<br />
# Paula Gray-Overtoom<br />
# Liz Milewicz<br />
# Michael Doran<br />
# Caitlin Christian-Lamb<br />
# [[User:RileyChilds|Riley Childs]]<br />
----<br />
<br />
=== Archival discovery and use ===<br />
'''Full Day''' <br />
<br />
Contacts: <br />
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br />
* Will Sexton, Duke, will.sexton at duke.edu<br />
<br />
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br />
<br />
Morning agenda: focused talks around (but not limited to) issues such as:<br />
* Crowd-sourcing description to enhance collecitons<br />
* Linked data and authority<br />
* Mass digitization and sustainable workflows<br />
* Digitized objects in context (images and other objects in finding aids)<br />
* Too many cooks in the kitchen: versioning<br />
* Global-, intra-, and inter- discovery of archival materials via finding aids <br />
* and more...<br />
<br />
Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br />
<br />
Tool examples:<br />
* Archivespace<br />
* STEADy<br />
* "RAMP" (Remixing Archival Metadata Project)<br />
* OpenRefine<br />
* Aeon<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 />
Morning:<br />
* Julia Bauder<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
<br />
# Josh Wilson<br />
# Sam Kome<br />
# Linda Ballinger<br />
# Caitlin Christian-Lamb<br />
# Laurie Lee Moses (seriously hard to decide here!)<br />
# David Bass<br />
----<br />
<br />
===AV Content Slam===<br />
'''Half-Day [morning]'''<br />
Contacts:<br />
* Kara Van Malssen, kara (at) avpreserve.com<br />
* Lauren Sorenson, laurens (at) bavc.org<br />
* Steven Villereal , villereal (at) gmail.com<br />
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br />
Possible topics of discussion might include:<br />
* Use of format id and characterization/metadata extraction tools for AV<br />
* Creating and using time-based metadata<br />
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br />
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# A. Soroka<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [afternoon]<br />
<br />
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br />
<br />
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
<br />
----<br />
<br />
<br />
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br />
'''Half-Day [tbd - probably afternoon]'''<br />
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br />
<br />
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br />
<br />
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# Charlie Morris (NCSU)<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Liz Milewicz<br />
# Scott Hanrath<br />
# Mike Beccaria<br />
# Sean Aery<br />
# Carolina Garcia<br />
# Heidi Frank<br />
----<br />
<br />
===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===<br />
<br />
Presenter: Eddie Newwirth and presenters from Summon libraries<br />
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)<br />
<br />
The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.<br />
<br />
The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.<br />
<br />
The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=402122014 preconference proposals2014-01-06T15:27:12Z<p>Ajconsta: added Summon camp details</p>
<hr />
<div>= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. <br />
<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".<br />
<br />
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." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
=Code4Lib 2014 Pre-Conference Proposals=<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
<br />
* Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
* Kevin Reiss<br />
* Charlie Morris (NCSU) - glad to see this again this year!<br />
* Paula Gray-Overtoom<br />
* Laurie Lee Moses<br />
<br />
=====Afternoon=====<br />
<br />
&nbsp;<br />
<br />
----<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
<ol><br />
<li>Adam Constabaris<br />
<li>Ray Schwartz<br />
<li>Jason Stirnaman<br />
<li>Joshua Gomez<br />
<li>Sam Kome<br />
<li>Mike Beccaria<br />
<li>Angela Zoss<br />
<li>A. Soroka<br />
</ol><br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
# Bret Davidson<br />
# Coral Sheldon-Hess<br />
# Cory Lown<br />
# Emily Daly<br />
# Angela Zoss<br />
# Sean Aery<br />
----<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
# Shaun Ellis<br />
# Kevin Reiss<br />
# Megan Kudzia<br />
# Erik Hatcher<br />
# Emily Daly<br />
# Laurie Lee Moses<br />
<br />
----<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<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! 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 Blacklight and Hydra.<br />
<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 />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Caitlin Christian-Lamb<br />
<br />
4. Scott Bacon<br />
<br />
5. [[User:RileyChilds | Riley Childs]]<br />
<br />
6. Carolina Garcia<br />
<br />
----<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<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 />
# Robin Dean<br />
# Erin White<br />
# Andrew Darby<br />
# Sam Kome<br />
# Ryan Scherle<br />
# Will Shaw<br />
# Liz Milewicz<br />
# Cynthia "Arty" Ng<br />
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)<br />
----<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* 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?<br />
* 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?<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 />
#Bret Davidson<br />
#Mike Graves<br />
#Ray Schwartz<br />
#Jason Stirnaman<br />
#Julia Bauder<br />
#Linda Ballinger<br />
#Scott Hanrath<br />
#Caitlin Christian-Lamb<br />
#Ian Walls<br />
#Scott Bacon <br />
<br />
----<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
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. <br />
<br />
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.<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 />
# Devon Smith<br />
# Kevin S. Clarke<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Carolina Garcia<br />
----<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
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:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<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 />
# Esmé Cowles<br />
----<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
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?<br />
<br />
Lots of tough questions.<br />
<br />
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.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
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<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 />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming (I'd be good with a half day too)<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
<br />
4. Cory Lown<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<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 />
# Michael Doran<br />
----<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
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:<br />
* 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.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* 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)<br />
<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 />
# Declan Fleming<br />
# Esmé Cowles<br />
# Jason Stirnaman<br />
# Ray Schwartz<br />
# Liz Milewicz<br />
----<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<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 />
# Sam Kome<br />
# Paula Gray-Overtoom<br />
# Liz Milewicz<br />
# Michael Doran<br />
# Caitlin Christian-Lamb<br />
# [[User:RileyChilds|Riley Childs]]<br />
----<br />
<br />
=== Archival discovery and use ===<br />
'''Full Day''' <br />
<br />
Contacts: <br />
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br />
* Will Sexton, Duke, will.sexton at duke.edu<br />
<br />
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br />
<br />
Morning agenda: focused talks around (but not limited to) issues such as:<br />
* Crowd-sourcing description to enhance collecitons<br />
* Linked data and authority<br />
* Mass digitization and sustainable workflows<br />
* Digitized objects in context (images and other objects in finding aids)<br />
* Too many cooks in the kitchen: versioning<br />
* Global-, intra-, and inter- discovery of archival materials via finding aids <br />
* and more...<br />
<br />
Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br />
<br />
Tool examples:<br />
* Archivespace<br />
* STEADy<br />
* "RAMP" (Remixing Archival Metadata Project)<br />
* OpenRefine<br />
* Aeon<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 />
Morning:<br />
* Julia Bauder<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
<br />
# Josh Wilson<br />
# Sam Kome<br />
# Linda Ballinger<br />
# Caitlin Christian-Lamb<br />
# Laurie Lee Moses (seriously hard to decide here!)<br />
----<br />
<br />
===AV Content Slam===<br />
'''Half-Day [morning]'''<br />
Contacts:<br />
* Kara Van Malssen, kara (at) avpreserve.com<br />
* Lauren Sorenson, laurens (at) bavc.org<br />
* Steven Villereal , villereal (at) gmail.com<br />
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br />
Possible topics of discussion might include:<br />
* Use of format id and characterization/metadata extraction tools for AV<br />
* Creating and using time-based metadata<br />
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br />
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# A. Soroka<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [afternoon]<br />
<br />
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br />
<br />
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
<br />
----<br />
<br />
<br />
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br />
'''Half-Day [tbd - probably afternoon]'''<br />
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br />
<br />
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br />
<br />
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# Charlie Morris (NCSU)<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Liz Milewicz<br />
# Scott Hanrath<br />
# Mike Beccaria<br />
# Sean Aery<br />
# Carolina Garcia<br />
----<br />
<br />
===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===<br />
<br />
Presenter: Eddie Newwirth and presenters from Summon libraries<br />
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)<br />
<br />
The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.<br />
<br />
The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.<br />
<br />
The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400742014 preconference proposals2013-12-07T10:33:33Z<p>Ajconsta: /* Code4Lib 2014 Pre-Conference Proposals */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
= PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
<br />
<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br />
<br />
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." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<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 />
----<br />
<br />
<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
Kevin Reiss<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
Adam Constabaris<br />
<br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
#Bret Davidson<br />
#Coral Sheldon-Hess<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
1. Shaun Ellis<br />
2. Kevin Reiss<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<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! 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 Blacklight and Hydra.<br />
<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 />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<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 />
1. Robin Dean<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* 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?<br />
* 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?<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 />
#Bret Davidson<br />
<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
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. <br />
<br />
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.<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 />
# Devon Smith<br />
# Kevin S. Clarke<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
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:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<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 />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
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?<br />
<br />
Lots of tough questions.<br />
<br />
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.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
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<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 />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<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 />
----<br />
<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
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:<br />
* 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.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* 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)<br />
<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 />
Declan Fleming<br />
<br />
----<br />
<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<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 />
----<br />
<br />
=== Archival discovery and use ===<br />
'''Full Day''' <br />
<br />
Contacts: <br />
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br />
* Will Sexton, Duke, will.sexton at duke.edu<br />
<br />
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br />
<br />
Morning agenda: focused talks around (but not limited to) issues such as:<br />
* Crowd-sourcing description to enhance collecitons<br />
* Linked data and authority<br />
* Mass digitization and sustainable workflows<br />
* Digitized objects in context (images and other objects in finding aids)<br />
* Too many cooks in the kitchen: versioning<br />
* Global-, intra-, and inter- discovery of archival materials via finding aids <br />
* and more...<br />
<br />
Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br />
<br />
Tool examples:<br />
* Archivespace<br />
* STEADy<br />
* "RAMP" (Remixing Archival Metadata Project)<br />
* OpenRefine<br />
* Aeon<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 />
Morning:<br />
* your name<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
* your name<br />
<br />
----<br />
<br />
===AV Content Slam===<br />
'''Half-Day [morning]'''<br />
Contacts:<br />
* Kara Van Malssen, kara (at) avpreserve.com<br />
* Lauren Sorenson, laurens (at) bavc.org<br />
* Steven Villereal , villereal (at) gmail.com<br />
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br />
Possible topics of discussion might include:<br />
* Use of format id and characterization/metadata extraction tools for AV<br />
* Creating and using time-based metadata<br />
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br />
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [afternoon]<br />
<br />
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br />
<br />
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
<br />
----<br />
<br />
<br />
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br />
'''Half-Day [tbd - probably afternoon]'''<br />
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br />
<br />
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br />
<br />
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
===Summon Camp===<br />
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)<br />
Description to be provided by Gillian after account issues resolved. <br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400622014 preconference proposals2013-12-06T15:01:30Z<p>Ajconsta: /* Open Refine Hackfest */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br />
<br />
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." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<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 />
----<br />
<br />
<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
Kevin Reiss<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
Adam Constabaris<br />
<br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
#Bret Davidson<br />
#Coral Sheldon-Hess<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
1. Shaun Ellis<br />
2. Kevin Reiss<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<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! 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 Blacklight and Hydra.<br />
<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 />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<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 />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* 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?<br />
* 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?<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 />
#Bret Davidson<br />
<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
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. <br />
<br />
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.<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 />
# Devon Smith<br />
# Kevin S. Clarke<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
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:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<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 />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
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?<br />
<br />
Lots of tough questions.<br />
<br />
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.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
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<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 />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<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 />
----<br />
<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
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:<br />
* 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.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* 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)<br />
<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 />
Declan Fleming<br />
<br />
----<br />
<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<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 />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400472014 preconference proposals2013-12-02T20:02:55Z<p>Ajconsta: /* Registration for a pre-conference will require a small fee due at the time of registration. */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
<br />
<br />
== Attendance at a pre-conference will require a small fee ''due at the time of conference registration.'' ==<br />
<br />
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." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
=TEMPLATE=<br />
<br />
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. <br />
<br />
Pitch Format:<br />
<br />
----<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<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 />
----<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<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! 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 Blacklight and Hydra.<br />
<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 />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400462014 preconference proposals2013-12-02T19:57:08Z<p>Ajconsta: /* Note */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
<br />
<br />
== Registration for a pre-conference will require a small fee ''due at the time of registration.'' ==<br />
<br />
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."<br />
<br />
<br />
----<br />
<br />
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. <br />
<br />
Pitch Format:<br />
<br />
----<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<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 />
----<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<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! 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 Blacklight and Hydra.<br />
<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 />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400452014 preconference proposals2013-12-02T19:56:17Z<p>Ajconsta: </p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
<br />
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."<br />
<br />
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. <br />
<br />
Pitch Format:<br />
<br />
----<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<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 />
----<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<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 />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <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 />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<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 />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
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.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<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 />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<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 />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<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! 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 Blacklight and Hydra.<br />
<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 />
<br />
[[:Category:Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=396792014 preconference proposals2013-10-12T12:21:45Z<p>Ajconsta: Created page with "Code4Lib 2014 Pre-Conference Proposals (this space is currently blank) Pitch Format: hr. h2. NAME h3. "Full-Day|Half-Day" [PREFERRED TIME] p. Description h4. Interested in A..."</p>
<hr />
<div>Code4Lib 2014 Pre-Conference Proposals<br />
<br />
(this space is currently blank)<br />
<br />
<br />
Pitch Format:<br />
<br />
hr.<br />
h2. NAME<br />
h3. "Full-Day|Half-Day" [PREFERRED TIME]<br />
p. Description<br />
<br />
h4. Interested in Attending<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here</div>Ajconstahttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39235Code4Lib 2014 Conference Planning Volunteers2013-05-14T19:09:59Z<p>Ajconsta: /* Voting Activities Committee */</p>
<hr />
<div>= Code4Lib 2014 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
We hope to include at least one local person on each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling<br />
* Michael B. Klein (Pragmatic) and winner-picker app<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
* Jason Casden<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br />
<br />
* Kevin S. Clarke<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
* Adam Constabaris (NCSU)<br />
* Tim Shearer (UNC)<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Jason Raitz<br />
* Rosalyn Metz<br />
* Dre<br />
* Becky Yoose<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Tim McGeary (lead worrier)<br />
* Roy Tennant<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Robert H. McDonald (Indiana)<br />
* Sean Chen (Duke)<br />
* Thomas Dowling (Wake Forest)<br />
* Will Sexton (Duke)<br />
* Jeff Campbell (UNC-CH)<br />
* Brett Bonfield (Collingswood Public)<br />
<br />
== Streaming Video Committee ==<br />
<br />
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br />
<br />
- Francis Kayiwa<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference.<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
*Adam Constabaris (NCSU)<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Kevin S. Clarke<br />
* Dre<br />
<br />
== Wifi / Electrical / IRC Committee==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This is a newly proposed committee.<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39227Code4Lib 2014 Conference Planning Volunteers2013-05-14T13:54:26Z<p>Ajconsta: /* Voting Activities Committee */</p>
<hr />
<div>= Code4Lib 2014 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
We hope to include at least one local person on each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling<br />
* Michael B. Klein (Pragmatic) and winner-picker app<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
* Jason Casden<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br />
<br />
* Kevin S. Clarke<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Jason Raitz<br />
* Rosalyn Metz<br />
* Dre<br />
* Becky Yoose<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Tim McGeary (lead worrier)<br />
* Roy Tennant<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Robert H. McDonald (Indiana)<br />
* Sean Chen (Duke)<br />
* Thomas Dowling (Wake Forest)<br />
* Will Sexton (Duke)<br />
* Jeff Campbell (UNC-CH)<br />
* Brett Bonfield (Collingswood Public)<br />
<br />
== Streaming Video Committee ==<br />
<br />
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br />
<br />
- Francis Kayiwa<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference.<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
*Adam Constabaris<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Kevin S. Clarke<br />
* Dre<br />
<br />
== Wifi / Electrical / IRC Committee==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This is a newly proposed committee.<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39226Code4Lib 2014 Conference Planning Volunteers2013-05-14T13:53:37Z<p>Ajconsta: /* Voting Activities Committee */</p>
<hr />
<div>= Code4Lib 2014 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
We hope to include at least one local person on each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling<br />
* Michael B. Klein (Pragmatic) and winner-picker app<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
* Jason Casden<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br />
<br />
* Kevin S. Clarke<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Jason Raitz<br />
* Rosalyn Metz<br />
* Dre<br />
* Becky Yoose<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Tim McGeary (lead worrier)<br />
* Roy Tennant<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Robert H. McDonald (Indiana)<br />
* Sean Chen (Duke)<br />
* Thomas Dowling (Wake Forest)<br />
* Will Sexton (Duke)<br />
* Jeff Campbell (UNC-CH)<br />
* Brett Bonfield (Collingswood Public)<br />
<br />
== Streaming Video Committee ==<br />
<br />
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br />
<br />
- Francis Kayiwa<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference.<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
Adam Constabaris<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Kevin S. Clarke<br />
* Dre<br />
<br />
== Wifi / Electrical / IRC Committee==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This is a newly proposed committee.<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2014]]</div>Ajconstahttps://wiki.code4lib.org/index.php?title=2013_social_activities&diff=358172013 social activities2013-02-06T01:26:28Z<p>Ajconsta: </p>
<hr />
<div>== Ideas ==<br />
<br />
* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*<br />
** statsfool: sunday/monday/tuesday, either drinks or flight.<br />
** Amyhannah: monday/tuesday, drinks, probably not the flight.<br />
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced<br />
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.<br />
** [[User:pberry|pberry]]: any night but Wednesday (that's Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.<br />
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.<br />
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues. either drink or flight.<br />
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight<br />
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..<br />
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.<br />
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 12.--Newberry Library confirmed for February 14.<br />
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday.<br />
** escowles: I'm getting in around noon on Sunday, and interested in this.<br />
** pgrayove: I'm getting in around noon on Sunday too. I'm interested.<br />
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements.<br />
** kayiwa<br />
** Linda Ballinger<br />
** Courtney Greene<br />
** John Pillans<br />
** +6 from NCSU incl one Bret Davidson<br />
** Megan Kudzia<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Tuesday 2/12 ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> XML.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Tuesday evening (2/12)<br />
* Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders <br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
<br />
<br />
'''Restaurants'''<br />
<br />
<br />
'''Restaurants within .25 miles of the hotel'''<br />
<br />
[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)<br />
<br />
* Al Cornish - v (leader)<br />
* Carolyn Cole - n<br />
* Dileshni Jayasinghe - v<br />
* Will Clark - n<br />
* Adam Constabaris - v<br />
<br />
[http://www.dinerestaurant.com/ Dine] (Contemporary)<br />
<br />
<del>[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.</del> Totally booked.<br />
<br />
[http://littlegoatchicago.com/ Little Goat] - Izard just opened a diner across the street from G&G that is walk-in only.<br />
<br />
[http://www.haymarketbrewing.com/ Haymarket Pub & Brewery] (Pub food)<br />
<br />
[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)<br />
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.<br />
<br />
*Jason Ronallo (leader)- v<br />
*Alicia Cozine - n<br />
*Mark Mounts - v<br />
*Barbara Hui - n<br />
*Amy Deschenes - n<br />
*Adam Strohm - n<br />
* '''Capped at 6'''<br />
<br />
[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)<br />
<br />
[http://www.pegasuschicago.com/index.php Pegasus] (Greek)<br />
<br />
[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm. Let's meet in the hotel lobby at 6pm and walk over from there.<br />
<br />
* Rosalyn Metz (leader) - v<br />
* [[User:highermath|Cary Gordon]] - v<br />
* [[User:Jacobandresen|Jacob Andresen]] - n<br />
* Karen Miller - n<br />
* Dre - v<br />
* Mahria Lebow - n<br />
* '''Capped at 6'''<br />
<br />
'''Restaurants between .25 miles and .5 miles of the hotel'''<br />
<br />
Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]<br />
<br />
* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.<br />
* Charlie Morris - n<br />
* Cory Lown - v<br />
* Carolina Garcia - n<br />
*<br />
*<br />
<br />
[http://avecrestaurant.com/# Avec] (Small plate)<br />
Family-style small plate and tapas. Great Yelp reviews. We'll meet in the conference hotel at 6:00 <strike>6:45</strike> (they don't take reservations, but have stuff to sip on if there's a wait). Less than 10 minute walk from hotel.<br />
<br />
* Shaun Ellis (leader) - v<br />
* Jon Stroop - v<br />
* Paula Gray-Overtoom - n<br />
* Emily Zervas - n<br />
* Cynthia Ng - neither<br />
* Sarah Dooley - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)<br />
<br />
[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)<br />
<br />
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm<br />
* Matt Cordial - v<br />
<br />
<br />
[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)<br />
<br />
[http://decero.hellotacos.com/ De Cero] (Mexican)<br />
<br />
[http://www.dragonflymandarin.com/ Dragonfly] (Chinese, sushi)<br />
<br />
[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...<br />
<br />
[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)<br />
<br />
[http://www.idreamoffalafel.com/ I Dream of Falafel] (Mediterranean)<br />
<br />
* Emily Lynema (leader) - v<br />
* Christie Peterson - n<br />
<br />
[http://www.jaipurchicago.com/ Jaipur] (Indian; Reservation made for 6 at 6:30 under "Andrew," no last name accepted)<br />
<br />
* Andrew Darby (leader) - v<br />
* Josh Wilson (joshwilsonnc at gmail) - n<br />
* Tim Thompson - n<br />
*<br />
*<br />
*<br />
<br />
[http://lasardine.com/ La Sardine] (French)<br />
<br />
[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.<br />
<br />
*Becky Yoose (leader) b dot yoose at gmail - v<br />
*May Chan - n<br />
*David Anderson - newby<br />
*Terry Brady - new<br />
* Dave Menninger - n<br />
*Shawn Carraway -n<br />
* '''Capped at 6'''<br />
<br />
[http://www.nellcoterestaurant.com/ Nellcôte] (French)<br />
<br />
[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)<br />
<br />
[http://thepublicanrestaurant.com/ The Publican] (Seafood)<br />
<br />
* Jay Luker (eater) - v - Rezzie is for 8pm<br />
* Mark Matienzo (tweeter) - v<br />
* Devon Smith (pickle eater) - repeat offender<br />
* Chris Sharp (dead horse beater) - v<br />
* Michael B. Klein (greeter) - v<br />
* Bill McMillin (meeter) - n<br />
* '''Capped at 6'''<br />
<br />
[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese)<br />
<br />
[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)<br />
<br />
[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)<br />
<br />
[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian) <br />
<br />
[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)<br />
<br />
<br />
'''Restaurants between .5 miles and .75 miles of the hotel'''<br />
<br />
[http://currentsontheriver.com/ Currents on the River] (Eclectic)<br />
<br />
[http://n9ne.com/ N9NE Steakhouse] (Steak)<br />
<br />
[http://www.verachicago.com/menu Vera Chicago] (Spanish)<br />
<br />
<br />
'''Restaurants between .75 miles and 1 mile of the hotel'''<br />
<br />
[http://www.theberghoff.com/default.aspx The Berghoff] (German)<br />
* Declan Fleming - v (leader) I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.<br />
* Dave Green - n <br />
* Steven Villereal - n<br />
* Peter Murray - v<br />
* Trey Terrell - n<br />
* Mike Giarlo - v<br />
* '''Capped at 6'''<br />
<br />
[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand. Either way, we'll depart at 7pm.<br />
: (''note: the drinks at the bar at frontera are very tasty.'')<br />
*Dan Suchy (leader and over-eater) - v<br />
*Matt Critchlow - v<br />
*Carmen Mitchell - v<br />
*Maureen Callahan - n<br />
*David Cliff - n<br />
* Patrick Berry - 3rd year red-shirt freshman<br />
* '''Capped at 6'''<br />
<br />
[http://www.nativefoods.com/ Native Foods] (Vegan)<br />
<br />
<br />
'''Restaurants more than 1 mile from the hotel'''<br />
<br />
<br />
[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)<br />
<br />
[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ)<br />
<br />
[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)<br />
<br />
[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)<br />
<br />
[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)<br />
<br />
[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.<br />
<br />
* Francis Kayiwa (knackered leader) - v<br />
* Megan O'Neill Kudzia - n<br />
* Esther Verreau - n<br />
<br />
=== Veg*n Dinner ===<br />
<br />
Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.<br />
<br />
Max *6* people per party this year.<br />
<br />
'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ "meat free since '83" <br />
Will they easily be able to accommodate 6 folks walking in?<br />
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St Chicago, IL 60657). <br />
# Jason Ronallo (jronallo@gmail.com)<br />
# Linda Ballinger (linda dot ballinger at gmail)<br />
# May Chan (msuicat at gmail dot com)<br />
# Demian Katz (demian DOT katz AT villanova DOT edu)<br />
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl. Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.<br />
# Cynthia Ng (cynthia dot s dot ng at gmail)<br />
Capped at 6<br />
<br />
=== Code4lib/Goose Island Brewing Pull Request ===<br />
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM<br />
<br />
More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]<br />
<br />
<br />
=== Non-beery get together ===<br />
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM<br />
<br />
'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]<br />
<br />
'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian<br />
<br />
'''Cost:''' $10 skate rental, people watching free<br />
<br />
Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.<br />
<br />
FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.<br />
<br />
# Chris Sharp (indicating interest)<br />
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)<br />
# Peter Murray<br />
# Shawn Carraway<br />
# Karen Coombs<br />
# Michael Levy<br />
# Christie Peterson<br />
<br />
=== Flying Trapeze ===<br />
'''When:''' Monday, 2/11, TBD<br />
<br />
'''Contact:''' rosalynmetz at gmail dot com<br />
<br />
No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib. There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well. If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class. If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.<br />
<br />
Trapeze classes are $57, last 2 hours, and are limited to 10 people. Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1. If we can get enough people interested before then, we can buy out a whole class. If not it'll be first come, first serve (along with the general public).<br />
<br />
If you're interested in signing up, feel free to add your name and contact info to the list below.<br />
<br />
'''''Sign Up List'''''<br />
# Jay Luker (first!)<br />
# Bill McMillin<br />
# Bess Sadler<br />
# Karen Coyle<br />
# Sibyl Schaefer<br />
# Rosalyn Metz (because I'm organizing)<br />
# Alicia Cozine<br />
# <br />
# <br />
#<br />
<br />
=== Game Night! ===<br />
<br />
Moved this from idea to an actual event. Still getting some details, but here's what we know:<br />
<br />
We have a conference room at the UIC library reserved for 7:30 on Tuesday the 11th. Not sure how late we'll play. I'll bring some board games and pick up some cards. List below were people who were interested in games and what games they are bringing.<br />
<br />
(Note, there's also some discussion on Cards Against Humanity. I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and curteous to those around you. I will probably be pondering this issue for a while)<br />
<br />
This will get updated more as I have time to spend on it.<br />
<br />
Game Night! Type of games might vary due to interest, could range from party games like Werewolf, Wits & Wagers, Telestrations, Taboo, Apples to Apples to perhaps more strategic games like De Vulgari Eloquentia or Eclipse. Jon Gorman is willing to bring some games, are you? Jon will try to send out an email soon to get some interest.<br />
** yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned...<br />
**danwho: I 'll bring the Cards Against Humanity set.<br />
**escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc.<br />
**jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.)<br />
** decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.)<br />
** csharp: I'm interested in playing games - whatever people bring. I almost always travel with a pack or two of playing cards ;-). Monday or Tuesday nights are fine.<br />
** moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work!<br />
** demiankatz: I'm always up for a game. I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir.<br />
** sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring. ++ on Cards against Humanity! Prefer non-conflict with beer night.<br />
** arty: so totally interested. Unfortunately, I have no games to contribute.<br />
** sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)<br />
** dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good. <br />
** smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.<br />
** jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.<br />
** ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro?<br />
** Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set]. <br />
** dgcliff: I'd be interested. Can bring Ticket to Ride.<br />
** mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.<br />
*** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)<br />
** duspal: In. My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others). Let me know ahead of time if anyone is interested, since they're all relatively big...<br />
**librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.<br />
**beatricep: Uno gets no respect. ;-) @librarywebchic: I have always wanted to learn to play Majhong. If you're still bringing it, I'm in!<br />
** jcraitz: I'm in after the newcomer dinner. I'll bring Citadels and Bang!<br />
<br />
== Social Map - Places of Interest==<br />
<br />
https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0<br />
<br />
== Local Events ==<br />
Events Listings<br />
* Chicago Reader http://www.chicagoreader.com/<br />
* The City of Chicago’s Events Guide: http://www.choosechicago.com/ <br />
* Metromix Chicago: http://chicago.metromix.com/events <br />
* Timeout Chicago: http://timeoutchicago.com/<br />
<br />
== Local Food ==<br />
== Local Drinks ==<br />
==Chicago Events Feb 10-14==<br />
<br />
=== Sunday February 10===<br />
Theater -[http://www.neofuturists.org/ Too Much Light Makes the Baby Go Blind] "...with its ever-changing "menu," is an attempt to perform 30 plays in 60 minutes. " 7pm.<br />
<br />
Theater - [http://www.chicagoreader.com/chicago/chunks/Event?oid=8557720 Chunks] : Funny, Heartbreaking, Gross. 7pm & BYOB!<br />
<br />
===Monday February 11===<br />
<br />
Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Tuesday, February 12===<br />
Field trip to the Read/Write Library (details to follow). 6-9 PM+<br />
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will also invite friends from Code for America to hang out and talk civic data.<br />
<br />
Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Wednesday, February 13===<br />
===Thursday, February 14===<br />
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.<br />
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org<br />
<br />
'''''Sign Up List'''''<br />
# Michael Doran - doran@uta.edu<br />
# William Denton - wtd@pobox.com<br />
# Wayne Schneider - wschneider@hclib.org<br />
# Matt Cordial - rev3lator [at] gmail.com<br />
# [name] - [email address]<br />
#<br />
<br />
[[Category:Code4Lib2013]]</div>Ajconsta