Code4Lib - User contributions [en]

Code4Lib 2023 Conference Committees

2023-03-02T15:33:50Z

Ksclarke:

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Pre-conferences: March 14, 2023 (Rabinowitz Building)
* Main conference: March 15-17, 2023 (Frist Campus Center)

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact
* Hillel Arnold - (harnold@rockarch.org) - Volunteer
* Chulin Meng - (chm213@lehigh.edu) - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* Yinlin Chen - (ylchen@vt.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* John DeLooper - (john.delooper@lehman.cuny.edu) - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* Jenn Cummings & Kathy Azevedo - (code4lib@concentra-cms.com) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* [[User:Khaley|Kathleen Haley]] - Primary Contact, Chair
* Kathryn Michaelis - (kmicha3@emory.edu) - Secondary Contact, CoChair
* [[User:Thatandromeda|Andromeda Yelton]] - Documentarian
* Ranti Junus - Volunteer
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey
* Tod Olson <tod@uchicago.edu> - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* Andrew Battelini - (abattel@emory.edu)- Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Emily Boss (eboss-at-unr-edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Scholarship Committee ==
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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* Yongming Wang - (wangyo@tcnj.edu) - Primary Contact, Chair
* - Secondary Contact, CoChair
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian
* Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2022_national_conference_annual_report.md.

'''Currently seeking one or two coordinators.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Anne Slaughter on Slack or via email (anne dot slaughter at railslibraries dot info).

== T-Shirt Committee ==
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. User sizes and preferences will be obtained as part of the registration process.

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* Kate Lynch - (katelynch@princeton.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Margaret Heller - (mheller1@luc.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Hardy Pottinger - hardy.pottinger@ucop.edu - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Kate Lynch - (katelynch@princeton.edu) - LPC Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* Caitlin Bakker - (caitlin.bakker@uregina.ca) - Secondary Contact, CoChair
* Ed Hill - (edhill@duck.com) - Documentarian
* Hilary Shiue (hilaryszuyinshiue@nypl.org) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib 2023 Conference Committees

2023-01-31T20:51:21Z

Ksclarke: added note about availability to help

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Pre-conferences: March 14, 2023 (Rabinowitz Building)
* Main conference: March 15-17, 2023 (Frist Campus Center)

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact
* Hillel Arnold - (harnold@rockarch.org) - Volunteer
* Chulin Meng - (chm213@lehigh.edu) - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* Yinlin Chen - (ylchen@vt.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* John DeLooper - (john.delooper@lehman.cuny.edu) - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* Jenn Cummings & Kathy Azevedo - (code4lib@concentra-cms.com) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* [[User:Khaley|Kathleen Haley]] - Primary Contact, Chair
* Kathryn Michaelis - (kmicha3@emory.edu) - Secondary Contact, CoChair
* [[User:Thatandromeda|Andromeda Yelton]] - Documentarian
* Ranti Junus - Volunteer
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey
* Tod Olson <tod@uchicago.edu> - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* Andrew Battelini - (abattel@emory.edu)- Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Emily Boss (eboss-at-unr-edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Scholarship Committee ==
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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* Yongming Wang - (wangyo@tcnj.edu) - Primary Contact, Chair
* - Secondary Contact, CoChair
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian
* Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2022_national_conference_annual_report.md.

'''Currently seeking one or two coordinators.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Anne Slaughter on Slack or via email (anne dot slaughter at railslibraries dot info).

== T-Shirt Committee ==
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. User sizes and preferences will be obtained as part of the registration process.

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* Kate Lynch - (katelynch@princeton.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Margaret Heller - (mheller1@luc.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Hardy Pottinger - hardy.pottinger@ucop.edu - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Kate Lynch - (katelynch@princeton.edu) - LPC Volunteer
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer (didn't register before conference sold out, but I can still assist with post-processing/posting).
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* Caitlin Bakker - (caitlin.bakker@uregina.ca) - Secondary Contact, CoChair
* Ed Hill - (edhill@duck.com) - Documentarian
* Hilary Shiue (hilaryszuyinshiue@nypl.org) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib 2023 Conference Committees

2022-10-07T15:22:15Z

Ksclarke: Add myself as a video helper

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Dates: TBD

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* NAME - (EMAIL) - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Scholarship Committee ==
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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== T-Shirt Committee ==
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. User sizes and preferences will be obtained as part of the registration process.

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

User:Ksclarke

2022-10-06T21:47:11Z

Ksclarke: Add small formatting fixes

Kevin S. Clarke

Digital Library Software Developer / Services Team Lead Developer 
UCLA Library, Los Angeles, CA (though I work remotely from Boone, NC) 

ksclarke@ksclarke.io (preferred email) 
ksclarke@gmail.com (being phased out)

User:Ksclarke

2022-10-06T21:45:27Z

Ksclarke: Updated contact information

Kevin S. Clarke

Digital Library Software Developer / Services Team Lead Developer
UCLA Library, Los Angeles, CA (though I work remotely from NC)

ksclarke@gmail.com (being phased out)
ksclarke@ksclarke.io

User:Ksclarke

2017-02-21T23:15:53Z

Ksclarke: Add user page

Kevin S. Clarke

Digital Library Developer, UCLA Library

ksclarke@gmail.com

2017 Conference Volunteers

2017-02-21T23:14:10Z

Ksclarke: Added videostream volunteer

= Code4Lib 2017 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the conference planning committees.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the Los Angeles area (or know it very well), you can pick up a {insert color} "Local Guide" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

== Conference Logistics ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Monday 3/6:
* 8a-12p: [mailto:bobbi_fox@harvard.edu Bobbi Fox]
* 12p-4p: [mailto:lolliffe@getty.edu Lawrence Olliffe]

Tuesday 3/7:
* 8a-12p: [mailto:amy.wickner@gmail.com Amy Wickner], ''Your Name Here''

== Preconference Setup & Sessions==
Help manage preconference sessions, setting up projectors, etc.

Preconference Setup Monday 3/6:
* 8a-9:30a: 6 UCLA
* 12:30p-2p: 6 UCLA

Preconference Sessions Monday 3/6:
* 11:45a-12:15p at Powell: ''Your Name Here''
* 11:45a-12:15p at Young: ''Your Name Here''
* 11:45a-12:15p at Science & Engineering Library: ''Your Name Here''

* 4:15p-4:45p at Powell: ''Your Name Here''
* 4:15p-4:45p at Young: [mailto:kimpham54@gmail.com Kim Pham]
* 4:15p-4:45p at Science & Engineering Library: ''Your Name Here'', ''Your Name Here''

== Social Events ==
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc.

Wednesday 3/8:
* 6p-9p: ''Your Name Here''
* 8p-11p: ''Your Name Here''

== Social Networking ==
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.

Tuesday 3/7:
* 8a-12p: ''Your Name Here''
* 1p-5p: ''Your Name Here''

Wednesday 3/8:
* 8a-12p: ''Your Name Here''
* 1p-5p: ''Your Name Here''

Thursday 3/9:
* 8a-12p: ''Your Name Here''

== Mic-minders ==
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)

Tuesday 3/7:
* 9a-12p: ''Your Name Here''
* 1p-5p: [mailto:mheller1@luc.edu Margaret Heller]

Wednesday 3/8:
* 9a-12p: [mailto:amy.wickner@gmail.com Amy Wickner]
* 1p-5p: ''Your Name Here''

Thursday 3/9:
* 9a-12p: ''Your Name Here''

== Livestream Assistants (Onsite) ==
Livestream assitants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!

Tuesday 3/7:
* 8a-12p: [mailto:mlevy@ushmm.org Michael Levy]
* 8a-12p: [[User:Khaley|Kathleen Haley]]

* 12:30p-5p: ''Your Name Here''
* 12:30p-5p: ''Your Name Here''

Wednesday 3/8:
* 8a-12p: [[User:Khaley|Kathleen Haley]]
* 8a-12p: ''Your Name Here''

* 12:30p-5p: ''Your Name Here''
* 12:30p-5p: [[User:ksclarke|Kevin S. Clarke]]

Thursday 3/9:
* 8a-12p: ''Your Name Here''
* 8a-12p: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world.

Tuesday 3/7:
* 9a-12p: [mailto:jswierc1@swarthmore.edu Julie Swierczek] (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)
* 1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)

Wednesday 3/8:
* 9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)
* 1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)

Thursday 3/9:
* 9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.

* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]

Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]
* Your name here

==MCs==

Tuesday 3/7
* AM: [[User:Yoosebj|Becky]], who shall continue her reign as Destroyer of Names.
* PM: [[User:rtennant|Roy Tennant]], who studies at the feet of the Destroyer of Names.

Wednesday 3/8
* AM: Dre, but feel free to boot me if someone desperately wants to MC and slots are full.
* PM1: [[User:highermath|Cary Gordon]]
* PM2: ''Your Name Here''

Thursday 3/9
* AM: ''Your Name Here''

== Session Timers ==
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.

Tuesday AM
* Primary: ''Your Name Here''
* Backup: ''Your Name Here''

Tuesday PM
* Primary: [[User:Phette23|Eric Phetteplace]]
* Backup: ''Your Name Here''

Wednesday AM
* Primary: [mailto:hsherid2@illinois.edu Helenmary Sheridan]
* Backup: ''Your Name Here''

Wednesday PM
* Primary: [[User:Phette23|Eric Phetteplace]]
* Backup: ''Your Name Here''

Thursday AM
* Primary: ''Your Name Here''
* Backup: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Lawrence Olliffe
* [mailto:bobbi_fox@harvard.edu Bobbi Fox]
* [mailto:mheller1@luc.edu Margaret Heller]
* [mailto:matt.r.sherman@gmail.com Matt Sherman]
* ''Your Name Here''

[[Category: Code4Lib2017]]

2015 Preconference Proposals

2015-01-14T18:39:57Z

Ksclarke: Changed ksclarke's afternoon slot

Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions.

== Preconference Schedule (draft) ==
There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (40: Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp (5)
|-
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop (34: Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)
|-
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)
|}

== Pre-conferences ==
===MORNING:===
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====
Morning, Galleria I
* Terry Brady, Georgetown University Library, twb27@georgetown.edu

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''
# Megan Kudzia

====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====
Morning, Parlor A
* Karen A. Coombs, OCLC, coombsk@oclc.org

Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''
# Peggy Griesinger
# Ray Schwartz
# Josh Wilson

==== Delivering and Preserving GIS Data ====
Morning, Council
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''
# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger

====Linked Data Workshop====
Morning, Studio
* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''
# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean
# Naomi Dushay (probably)
# David Lacy
# David Uspal
# David Bass
# Brendan Quinn
# Chrissy Rissmeyer
# Sharon Clapp
# Anjanette Young
# Brooke Sansosti

====RailsBridge: Intro to programming in Ruby on Rails====
Morning, Galleria II
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''
# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
# Bojana Skarich
#Sarah Bavier

====Replace yourself with a painfully complex bash script...or try Ansible====
Morning, Galleria III
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp
# Heidi Frank
# Anjanette Young

====Visualizing Library Data====
Morning, Grand Ballroom II
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''
# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine
# Steve Meyer
# Matt Critchlow
# Andrew Pasterfield
# Ray Henry
# Bret Davidson
# Naomi Dushay (maybe)
# Eric Frierson
# Matt Bernhardt
# Greg Bem (Morning only)
# Dominic Bordelon

===FULL DAY:===

====Code Retreat====
Full Day, Parlor B
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''
# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
# Matt Connolly
# James Van Mil
# Glen Horton

====Code4Arc ====
Full Day, Directors
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:
* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''
# Laney McGlohon - developer
# Shaun Ellis
# Ryan Rotter
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
# Liza Harrell-Edge - end-user

====code4lib/Write The Docs barcamp====
Full day, Parlor C
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''
'''Full day'''
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
# Jason Raitz

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Chris Sharp

===AFTERNOON:===
==== A hands-on introduction to GeoBlacklight ====
Afternoon, Council
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''
# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger

==== CollectionSpace: Getting it up and running at your museum ====
Afternoon, Galleria II
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
# Terry Brady
# Sharon Clapp

==== Dive into Hydra ====
Afternoon, Studio
* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''
# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
# David Bass
# Scott Fisher
# Brian E. Davis
# Sarah Bavier

==== DPLA API Workshop: ====
Afternoon, Grand Ballroom II
* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods
# Greg Bem
# Brooke Sansosti

==== Fail4Lib 2015 ====
Afternoon, Galleria I
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''
# Ray Schwartz
# Charlie Morris
# Emily Lynema
# Bret Davidson
# Hannah Sommers

==== Intro to Docker ====
Afternoon, Galleria III
* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''
# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts
# Matt Critchlow
# Ray Henry
# Eric Frierson
# Sara Amato
# David Lacy
# David Uspal
# Matt Bernhardt
# Brendan Quinn
# Anjanette Young
# Kevin S. Clarke

==== Intro to Git & possibly beyond ====
Afternoon, Parlor A
* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:
* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''
# Jeannie Graham
# Derek Merleaux
# Laurie Reeves
# Bojana Skarich
# Heidi Frank
# Jason Raitz
# Emily Lynema
# Brian E. Davis
# Dominic Bordelon

==== Presentations workshop ====
Afternoon, Grand Ballroom I
* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''
#Vicky Steeves

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-11-17T21:16:22Z

Ksclarke: /* code4lib/Write The Docs barcamp */

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conference Proposals ==

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
#
#
#
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
#
#
#
#
#
#
#
#

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess
#
#
#
#

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
#
#
#
#
#
#
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
#
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
#
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
#
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Kevin S. Clarke
#
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
#
#
#
#
#
#
#
#

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
#
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
#
#
#
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
#
#
#
#
#
#
#
#

=== UXtravaganza ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
#
#
#
#
#
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
#
#
#
#
#
#

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
#
#
#
#
#
#
#

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-11-17T21:11:54Z

Ksclarke:

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conference Proposals ==

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
#
#
#
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
#
#
#
#
#
#
#
#

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess
#
#
#
#

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
#
#
#
#
#
#
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
#
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
#
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
#
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
#
#
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
#
#
#
#
#
#
#
#

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
#
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
#
#
#
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
#
#
#
#
#
#
#
#

=== UXtravaganza ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
#
#
#
#
#
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
#
#
#
#
#
#

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
#
#
#
#
#
#
#

[[Category:Code4Lib2015]]

2015 Prepared Talk Proposals

2014-11-07T18:47:42Z

Ksclarke: /* Docker? VMs? EC2? Yes! With Packer.io */

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* Technical issues - Big issues in library technology that should be addressed or better understood
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

* Speaker's name, email address, and (optional) affiliation
* Second speaker's name, email address, and affiliation, if second speaker

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==

* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)

In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!

First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.

Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.

The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.

Both games will be demoed.

We have never presented at Code4lib.

== Do the Semantic FRBRoo ==
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island

[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?

At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe.

To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform.

== Our $50,000 Problem: Why Library School? ==
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation

57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]

Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.

According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.

What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?

As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.

This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.

== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University
* Rachel Wittmann, rwittma@clemson.edu, Clemson University

Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.

In this talk, we will discuss:
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes.
* The stumbling blocks experienced in that process and how they were resolved.
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects.
* A brief overview of the export and import functions and also current workflow practices within Providence.
* Future plans & the role of CollectiveAccess at Clemson University Libraries

== Getting ContentDM and Wordpress to Play Together ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University

Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.

ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.

Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.

In this presentation, I will demonstrate the current state of the plugin and discuss future plans.

==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data from multiple unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

* Bess Sadler, bess@stanford.edu, Stanford University Libraries

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mb at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==

* Ashley Blewer!, ashley.blewer@gmail.com

Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?

== Level Up Your Coding with Code Club (yes, you can talk about it) ==

* Coral Sheldon-Hess, coral@sheldon-hess.org

Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.

But you don't have to read code alone! (Which is good. It's really not fun to read code alone.)

In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground!

== The Growth of a Programmer ==

* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu

Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.

== Developing a Fedora 4.0 Content Model for Disk Images ==

* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager

As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.

== Data acquisition and publishing tools in R ==

* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter

R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).

== SPLUNK: Log File Analysis ==

* Jim LeFager, jlefager@depaul.edu, DePaul University Library
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.

== Your code does not exist in a vacuum ==
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)

“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009

In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum.

Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.

This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.

tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.

== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==

* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago

The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content.

All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.

http://chicagocollectionsconsortium.org

== Programmers are not projects: lessons learned from managing humans ==

* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter

Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.

== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==

* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore

Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators?

There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.

== A Semantic Makeover for CMS Data ==

* Bill Levay, wjlevay@gmail.com, Linked Jazz Project

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

== Taking User Experience (UX) to new heights ==

* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University

User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:

- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.

- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.

- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.

This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.

==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==

*Margaret Heller, Loyola University Chicago, mheller1@luc.edu
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu
*May Yan, Ryerson University, may.yan@ryerson.ca

Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities.

This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996:
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.”

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.

==Making your digital objects embeddable around the web==

* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.

In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.

==So you want to make your geospatial data discoverable==

* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.

== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==

* Adam Wead, awead@psu.edu, Penn State University

Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a
working solution that exhibited all the hallmarks of good testing and software design.

This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the
problem instead of just describing what the code should do. It was also essential to begin testing from an integration
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.

== Designing and Leading a Kick A** Tech Team ==

* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center

New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.

==American (Archives) Horror Story: LTO Failure and Data Loss ==

* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH

Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!

== PBCore in Action: Three Words, Not Two! ==

* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH

In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.

At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore

==Docker? VMs? EC2? Yes! With Packer.io==

* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA

There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!

== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==

* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)

I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.

At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.

Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.

This talk will explore the following questions:

* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.

* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)

* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.

* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”

* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.

2015 Prepared Talk Proposals

2014-11-07T18:44:57Z

Ksclarke: /* Docker? VMs? EC2? Yes! With Packer.io */

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* Technical issues - Big issues in library technology that should be addressed or better understood
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

* Speaker's name, email address, and (optional) affiliation
* Second speaker's name, email address, and affiliation, if second speaker

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==

* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)

In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!

First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.

Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.

The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.

Both games will be demoed.

We have never presented at Code4lib.

== Do the Semantic FRBRoo ==
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island

[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?

At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe.

To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform.

== Our $50,000 Problem: Why Library School? ==
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation

57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]

Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.

According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.

What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?

As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.

This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.

== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University
* Rachel Wittmann, rwittma@clemson.edu, Clemson University

Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.

In this talk, we will discuss:
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes.
* The stumbling blocks experienced in that process and how they were resolved.
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects.
* A brief overview of the export and import functions and also current workflow practices within Providence.
* Future plans & the role of CollectiveAccess at Clemson University Libraries

== Getting ContentDM and Wordpress to Play Together ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University

Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.

ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.

Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.

In this presentation, I will demonstrate the current state of the plugin and discuss future plans.

==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data from multiple unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

* Bess Sadler, bess@stanford.edu, Stanford University Libraries

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mb at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==

* Ashley Blewer!, ashley.blewer@gmail.com

Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?

== Level Up Your Coding with Code Club (yes, you can talk about it) ==

* Coral Sheldon-Hess, coral@sheldon-hess.org

Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.

But you don't have to read code alone! (Which is good. It's really not fun to read code alone.)

In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground!

== The Growth of a Programmer ==

* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu

Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.

== Developing a Fedora 4.0 Content Model for Disk Images ==

* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager

As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.

== Data acquisition and publishing tools in R ==

* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter

R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).

== SPLUNK: Log File Analysis ==

* Jim LeFager, jlefager@depaul.edu, DePaul University Library
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.

== Your code does not exist in a vacuum ==
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)

“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009

In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum.

Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.

This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.

tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.

== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==

* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago

The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content.

All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.

http://chicagocollectionsconsortium.org

== Programmers are not projects: lessons learned from managing humans ==

* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter

Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.

== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==

* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore

Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators?

There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.

== A Semantic Makeover for CMS Data ==

* Bill Levay, wjlevay@gmail.com, Linked Jazz Project

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

== Taking User Experience (UX) to new heights ==

* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University

User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:

- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.

- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.

- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.

This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.

==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==

*Margaret Heller, Loyola University Chicago, mheller1@luc.edu
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu
*May Yan, Ryerson University, may.yan@ryerson.ca

Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities.

This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996:
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.”

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.

==Making your digital objects embeddable around the web==

* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.

In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.

==So you want to make your geospatial data discoverable==

* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.

== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==

* Adam Wead, awead@psu.edu, Penn State University

Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a
working solution that exhibited all the hallmarks of good testing and software design.

This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the
problem instead of just describing what the code should do. It was also essential to begin testing from an integration
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.

== Designing and Leading a Kick A** Tech Team ==

* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center

New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.

==American (Archives) Horror Story: LTO Failure and Data Loss ==

* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH

Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!

== PBCore in Action: Three Words, Not Two! ==

* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH

In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.

At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore

==Docker? VMs? EC2? Yes! With Packer.io==

* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA

There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). And, as an added value, all the buzzwords in this proposal will be defined and explained!

== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==

* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)

I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.

At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.

Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.

This talk will explore the following questions:

* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.

* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)

* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.

* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”

* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.

2015 Prepared Talk Proposals

2014-11-07T18:43:44Z

Ksclarke: /* Docker? VMs? EC2? Yes! With Packer.io */

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* Technical issues - Big issues in library technology that should be addressed or better understood
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

* Speaker's name, email address, and (optional) affiliation
* Second speaker's name, email address, and affiliation, if second speaker

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==

* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)

In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!

First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.

Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.

The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.

Both games will be demoed.

We have never presented at Code4lib.

== Do the Semantic FRBRoo ==
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island

[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?

At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe.

To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform.

== Our $50,000 Problem: Why Library School? ==
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation

57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]

Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.

According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.

What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?

As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.

This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.

== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University
* Rachel Wittmann, rwittma@clemson.edu, Clemson University

Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.

In this talk, we will discuss:
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes.
* The stumbling blocks experienced in that process and how they were resolved.
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects.
* A brief overview of the export and import functions and also current workflow practices within Providence.
* Future plans & the role of CollectiveAccess at Clemson University Libraries

== Getting ContentDM and Wordpress to Play Together ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University

Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.

ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.

Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.

In this presentation, I will demonstrate the current state of the plugin and discuss future plans.

==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data from multiple unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

* Bess Sadler, bess@stanford.edu, Stanford University Libraries

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mb at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==

* Ashley Blewer!, ashley.blewer@gmail.com

Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?

== Level Up Your Coding with Code Club (yes, you can talk about it) ==

* Coral Sheldon-Hess, coral@sheldon-hess.org

Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.

But you don't have to read code alone! (Which is good. It's really not fun to read code alone.)

In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground!

== The Growth of a Programmer ==

* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu

Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.

== Developing a Fedora 4.0 Content Model for Disk Images ==

* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager

As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.

== Data acquisition and publishing tools in R ==

* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter

R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).

== SPLUNK: Log File Analysis ==

* Jim LeFager, jlefager@depaul.edu, DePaul University Library
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.

== Your code does not exist in a vacuum ==
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)

“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009

In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum.

Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.

This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.

tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.

== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==

* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago

The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content.

All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.

http://chicagocollectionsconsortium.org

== Programmers are not projects: lessons learned from managing humans ==

* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter

Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.

== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==

* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore

Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators?

There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.

== A Semantic Makeover for CMS Data ==

* Bill Levay, wjlevay@gmail.com, Linked Jazz Project

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

== Taking User Experience (UX) to new heights ==

* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University

User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:

- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.

- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.

- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.

This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.

==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==

*Margaret Heller, Loyola University Chicago, mheller1@luc.edu
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu
*May Yan, Ryerson University, may.yan@ryerson.ca

Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities.

This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996:
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.”

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.

==Making your digital objects embeddable around the web==

* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.

In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.

==So you want to make your geospatial data discoverable==

* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.

== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==

* Adam Wead, awead@psu.edu, Penn State University

Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a
working solution that exhibited all the hallmarks of good testing and software design.

This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the
problem instead of just describing what the code should do. It was also essential to begin testing from an integration
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.

== Designing and Leading a Kick A** Tech Team ==

* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center

New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.

==American (Archives) Horror Story: LTO Failure and Data Loss ==

* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH

Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!

== PBCore in Action: Three Words, Not Two! ==

* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH

In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.

At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore

==Docker? VMs? EC2? Yes! With Packer.io==

* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA

There are a lot of exciting ways to deploy a stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). And, as an added value, all the buzzwords in this proposal will be defined and explained!

== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==

* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)

I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.

At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.

Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.

This talk will explore the following questions:

* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.

* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)

* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.

* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”

* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.

2015 Prepared Talk Proposals

2014-11-07T18:43:09Z

Ksclarke: /* Docker? VMs? EC2? Yes! With Packer.io */

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* Technical issues - Big issues in library technology that should be addressed or better understood
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

* Speaker's name, email address, and (optional) affiliation
* Second speaker's name, email address, and affiliation, if second speaker

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==

* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)

In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!

First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.

Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.

The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.

Both games will be demoed.

We have never presented at Code4lib.

== Do the Semantic FRBRoo ==
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island

[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?

At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe.

To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform.

== Our $50,000 Problem: Why Library School? ==
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation

57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]

Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.

According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.

What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?

As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.

This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.

== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University
* Rachel Wittmann, rwittma@clemson.edu, Clemson University

Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.

In this talk, we will discuss:
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes.
* The stumbling blocks experienced in that process and how they were resolved.
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects.
* A brief overview of the export and import functions and also current workflow practices within Providence.
* Future plans & the role of CollectiveAccess at Clemson University Libraries

== Getting ContentDM and Wordpress to Play Together ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University

Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.

ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.

Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.

In this presentation, I will demonstrate the current state of the plugin and discuss future plans.

==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data from multiple unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

* Bess Sadler, bess@stanford.edu, Stanford University Libraries

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mb at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==

* Ashley Blewer!, ashley.blewer@gmail.com

Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?

== Level Up Your Coding with Code Club (yes, you can talk about it) ==

* Coral Sheldon-Hess, coral@sheldon-hess.org

Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.

But you don't have to read code alone! (Which is good. It's really not fun to read code alone.)

In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground!

== The Growth of a Programmer ==

* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu

Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.

== Developing a Fedora 4.0 Content Model for Disk Images ==

* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager

As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.

== Data acquisition and publishing tools in R ==

* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter

R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).

== SPLUNK: Log File Analysis ==

* Jim LeFager, jlefager@depaul.edu, DePaul University Library
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.

== Your code does not exist in a vacuum ==
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)

“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009

In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum.

Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.

This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.

tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.

== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==

* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago

The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content.

All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.

http://chicagocollectionsconsortium.org

== Programmers are not projects: lessons learned from managing humans ==

* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter

Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.

== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==

* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore

Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators?

There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.

== A Semantic Makeover for CMS Data ==

* Bill Levay, wjlevay@gmail.com, Linked Jazz Project

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

== Taking User Experience (UX) to new heights ==

* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University

User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:

- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.

- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.

- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.

This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.

==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==

*Margaret Heller, Loyola University Chicago, mheller1@luc.edu
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu
*May Yan, Ryerson University, may.yan@ryerson.ca

Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities.

This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996:
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.”

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.

==Making your digital objects embeddable around the web==

* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.

In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.

==So you want to make your geospatial data discoverable==

* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.

== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==

* Adam Wead, awead@psu.edu, Penn State University

Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a
working solution that exhibited all the hallmarks of good testing and software design.

This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the
problem instead of just describing what the code should do. It was also essential to begin testing from an integration
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.

== Designing and Leading a Kick A** Tech Team ==

* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center

New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.

==American (Archives) Horror Story: LTO Failure and Data Loss ==

* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH

Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!

== PBCore in Action: Three Words, Not Two! ==

* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH

In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.

At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore

==Docker? VMs? EC2? Yes! With Packer.io==

* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA

There are a lot of exciting ways to deploy a stack nowadays. Many of your systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). And, as an added value, all the buzzwords in this proposal will be defined and explained!

== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==

* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)

I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.

At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.

Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.

This talk will explore the following questions:

* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.

* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)

* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.

* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”

* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.

2015 Prepared Talk Proposals

2014-11-07T17:37:31Z

Ksclarke: Added proposal

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* Technical issues - Big issues in library technology that should be addressed or better understood
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

* Speaker's name, email address, and (optional) affiliation
* Second speaker's name, email address, and affiliation, if second speaker

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==

* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)

In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!

First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.

Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.

The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.

Both games will be demoed.

== Do the Semantic FRBRoo ==
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island

[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?

At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe.

To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform.

== Our $50,000 Problem: Why Library School? ==
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation

57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]

Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.

According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.

What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?

As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.

This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.

== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University
* Rachel Wittmann, rwittma@clemson.edu, Clemson University

Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.

In this talk, we will discuss:
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes.
* The stumbling blocks experienced in that process and how they were resolved.
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects.
* A brief overview of the export and import functions and also current workflow practices within Providence.
* Future plans & the role of CollectiveAccess at Clemson University Libraries

== Getting ContentDM and Wordpress to Play Together ==
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University

Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.

ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.

Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.

In this presentation, I will demonstrate the current state of the plugin and discuss future plans.

==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data from multiple unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

* Terry Brady, twb27@georgetown.edu, Georgetown University Library

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

* Bess Sadler, bess@stanford.edu, Stanford University Libraries

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mb at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==

* Ashley Blewer!, ashley.blewer@gmail.com

Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?

== Level Up Your Coding with Code Club (yes, you can talk about it) ==

* Coral Sheldon-Hess, coral@sheldon-hess.org

Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.

But you don't have to read code alone! (Which is good. It's really not fun to read code alone.)

In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground!

== The Growth of a Programmer ==

* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu

Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.

== Developing a Fedora 4.0 Content Model for Disk Images ==

* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager

As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.

== Data acquisition and publishing tools in R ==

* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter

R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).

== SPLUNK: Log File Analysis ==

* Jim LeFager, jlefager@depaul.edu, DePaul University Library
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.

== Your code does not exist in a vacuum ==
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)

“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009

In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum.

Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.

This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.

tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.

== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==

* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago

The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content.

All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.

http://chicagocollectionsconsortium.org

== Programmers are not projects: lessons learned from managing humans ==

* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter

Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.

== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==

* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore

Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators?

There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.

== A Semantic Makeover for CMS Data ==

* Bill Levay, wjlevay@gmail.com, Linked Jazz Project

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

== Taking User Experience (UX) to new heights ==

* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University

User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:

- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.

- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.

- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.

This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.

==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==

*Margaret Heller, Loyola University Chicago, mheller1@luc.edu
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu
*May Yan, Ryerson University, may.yan@ryerson.ca

Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities.

This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996:
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.”

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.

==Making your digital objects embeddable around the web==

* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.

In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.

==So you want to make your geospatial data discoverable==

* Jack Reed, pjreed@stanford.edu, Stanford University Libraries

Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.

== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==

* Adam Wead, awead@psu.edu, Penn State University

Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a
working solution that exhibited all the hallmarks of good testing and software design.

This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the
problem instead of just describing what the code should do. It was also essential to begin testing from an integration
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.

== Designing and Leading a Kick A** Tech Team ==

* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center

New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.

==American (Archives) Horror Story: LTO Failure and Data Loss ==

* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH

Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!

== PBCore in Action: Three Words, Not Two! ==

* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH

In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.

At this session, I'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore

==Docker? VMs? EC2? Yes! With Packer.io==

* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA

There are a lot of exciting ways to deploy a stack nowadays. Many of your systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder, and Graphite. And, as an added value, all the buzzwords in this proposal will be defined and explained!

Southeast

2014-04-09T15:38:11Z

Ksclarke: added mailing list

== Mailing List ==
There is a separate Code4Lib-SE (Southeast) mailing list for the planning of Southeast region Code4Lib meetups. Feel free to post Code4Lib-SE topics to the main Code4Lib mailing list as well (for instance, announcing new meetups) but this Code4Lib-SE specific mailing list will make sure we don't drown the main mailing list with other sorts of Code4Lib-SE administriva.

https://groups.google.com/forum/#!forum/code4lib-se

== Planning ==
Help us Plan!
Base Proposals
----
*Charlotte, NC
*Columbia, SC
*Greenville, SC

== Times ==
What Dates/Times work best for you?

2014 During the Conference Volunteers

2014-03-26T04:23:14Z

Ksclarke: /* Raffles */

code4lib 2014 During the Conference Volunteers

== Hospitality Suite Committee ==

This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.

== Welcome Wagon Committee ==

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.

* Becky Yoose (b.yoose at google)

== Social Networking ==
Responsible for non-IRC social networking presence.

1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.

Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.

Tuesday AM

Tuesday PM
* Coral Sheldon-Hess (@web_kunoichi on Twitter, coral on IRC)

Wednesday AM

Wednesday PM

Thursday AM

== IRC Evangelists ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

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".

If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.

* Becky Yoose (yo_bj in IRC)
* Riley Childs (rowdychildren)

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people
* Riley Childs (rowdychildren in irc) (7044972086 if serious issue)
* Jeff Campbell
STATUS
*Riley has contracted Freenode, waiting on confirmation from ops team (3/15)
*Riley Learned that we had been given a block of Class B private IP addresses, he is trying to get in contact with the Hotel Staff (3/18)

==Registration Desk Volunteers==

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.

Tuesday 8-9 am

Adam Constabaris (first dot last with the cases on the down-low at gmail)

==MCs==

Tuesday AM
* Cary, boring, but reliable. Somewhat taller than Becky.
''feel free to replace me with someone more interesting''

Tuesday PM

* Dre, destroyer of cookies, doesn't look as good in a hat as Becky.

Wednesday AM

*Becky, destroyer of last names, singer of badly adapted show tunes

Wednesday PM
*Rosalyn, destroyer of fun, not as entertaining as Becky

Thursday AM
* Cynthia, destroyer of jokes, babbler of the universe

== Session Timer Volunteers ==

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.

'''Schedule for Session Timers'''

Tuesday AM
* Francis Kayiwa
* Dan Kerchner

Tuesday PM
* Peter Murray
* Ranti Junus

Wednesday AM
* Maura Carbone
* Megan Kudzia

Wednesday PM
* Violeta Ilik
* William Hicks

Thursday AM
* Bret Davidson

== Raffles ==

* Michael Klein
* Bobbi Fox

== Assistance with Valerie Aurora's Keynote ==

We need 2-4 volunteers to pass out index cards and collect them back and deliver them to the stage.

*
*
*
*

== Whatever Else Needs to be Done ==

* Roy Tennant, royt in channel, text to 707-287-5580
* Riley Childs, rowdychildren, 7044972086 (I will do whatever, but I maybe running the stream.)
[[Category: Code4Lib2014]]

Code4Lib 2014 Conference Planning Volunteers

2014-03-18T13:57:11Z

Ksclarke: /* Book Give-Away Committee */

= Code4Lib 2014 Committees =

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. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We hope to include at least one local person on each committee.

A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.

The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).

== Book Give-Away Committee ==

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.

Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.

* Kevin S. Clarke (Manning) and general wrangling (nominated as lead) - no luck with books from Manning
* Michael B. Klein (Pragmatic) and winner-picker app
* Sarah Shealy (Packt) and general wrangling if/when needed - no luck with books from Packt
* Shaun Ellis (Rosenfeld Media and O'Reilly eBooks)

Current Status:
* O'Reilly is also offering a free ebook to all attendees. This is in the form of a printed voucher that should be bundled with the t-shirt and other swag. Shaun Ellis is responsible for the printing of the vouchers.
* Rosenfeld Media is shipping a number of giveaway titles directly to Tim McGeary a couple weeks before the conference.
* Pragmatic responds: "Thank you for thinking of us and contacting us again about providing give-away items. We are actually in the Raleigh area, and would be happy to coordinate a drop off of books for use as door prizes at the time of the conference." I will follow up with them closer to the conference date to coordinate a drop-off.

Shaun also mentioned that we have a prospectus this year that would be great to send along with our requests to the publishers. You can find it at: http://code4lib.org/files/Code4LibProspectus.pdf

== Keynote Speakers Committee ==

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.

Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013 
Keynote speaker voting - September 9, 2013 - September 20, 2013 
Have speakers finalized by November 15, 2013

* Jason Casden (NCSU) -- lead
* Tom Johnson (Johnson.tom@gmail.com)
* Bret Davidson (NCSU)
* Jeff Campbell (UNC)
* Joyce Chapman (State Library of NC)
* Dre (NCSU)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

* Kevin S. Clarke
* Kevin Beswick (NCSU)
* Yan Wang (NCCU)
* Kelly Leong (Duke)
* Dre (NCSU)
* Jason Raitz (NCSU)

== Pre-conference Committee ==

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.

Call for pre-conf proposals -- October 14, 2013 
Deadline for pre-conf proposals -- December 6, 2013 
Finalize pre-confs before registration opens -- January 3, 2014 
Send rosters to pre-conf organizers -- by February 21, 2014

* Adam Constabaris (NCSU) -- nominated as lead
* Tim Shearer (UNC)
* Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

Call for talk proposals -- October 14 - November 8, 2013 
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013 
Voting on talks -- November 18, 203 - December 6, 2013 
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013 
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!) 
Post final program schedule with talks - January 13, 2014

* Tom Johnson (Johnson.tom@gmail.com) -- lead
* Kevin Beswick (NCSU)
* Ranti Junus (ranti.junus@gmail.com)
* Roy Tennant (OCLC)
* Trevor Thornton (hellotrevorthornton@gmail.com)
* Lucas Mak (makw@mail.lib.msu.edu)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)
* Tod Olson (tod at uchicago dot edu)

== Scholarships Committee ==

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.

Call for applicants -- November 18, 2013 - December 13, 2013 
Determine winners -- December 14, 2014 - January 5, 2014 
Notify winners -- January 6, 2014 (must be before registration)

* Jason Ronallo (NCSU) -- lead
* Cory Lown (NCSU)
* Bohyun Kim (FIU)
* Santi Thompson (University of Houston) sathompson3@uh.edu
* Sarah Shealy (sarah.shealy@outlook.com)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Jason Raitz
* Rosalyn Metz
* Dre
* Becky Yoose
* Bohyun Kim

== Sponsorships Committee ==

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.

* Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)
* Roy Tennant (OCLC)
* Shaun Ellis (shaune@princeton.edu)
* Robert H. McDonald (Indiana)
* Sean Chen (Duke)
* Thomas Dowling (Wake Forest)
* Will Sexton (Duke)
* Jeff Campbell (UNC)
* Brett Bonfield (Collingswood Public)

== Streaming Video Committee ==
As of 12-18-2013 this committee has been combined with the Wifi/Electrical/IRC committee

== T-Shirt Committee ==

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. User sizes and preferences will be obtained as part of the registration process.

Call for T-shirt designs - December 2, 2014 - January 3, 2014 
Voting on T-shirt designs - January 13, 2014 - January 24, 2014 
Get bids based on sizes and design - January 27, 2014 - February 14, 2014 
Order t-shirts by February 17, 2014

*Charlie Morris (NCSU) -- lead
*Josh Wilson, State Library of NC (joshwilsonnc at gmail)

== Voting Activities Committee ==

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.

*Adam Constabaris (NCSU)

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Kevin S. Clarke
* Dre
* Ranti Junus
* [[User:LauraAkerman|Laura Akerman]], liblna@emory.edu

== Wifi / Electrical / IRC / Streaming Video Committee==

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, in addition the committee is responsible to work with the local hosts to figure out the requirements for video / streaming video and work to get final A/V estimates by late November 2013 to use for the final budget

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org
* [[User:RileyChilds|Riley Childs]], Riley@TFSGEO.com
* Francis Kayiwa
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)
* Jeff Campbell - UNC - CH

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2014]]

2014 AVGeeks Signup

2014-03-10T19:28:37Z

Ksclarke:

[http://www.avgeeks.com/wp2/ A/V Geeks] maintains a collection of over 23,000 old 16mm educational films from various decades of the 20th century, including such classics as [http://www.avgeeks.com/wp2/library-story-the-1952/ The Library Story (1952)], many obtained from school and government auctions. Media archaeologist [http://www.indyweek.com/indyweek/skip-elsheimer/Content?oid=1183990 Skip Elsheimer] holds themed showings of selected films at events around the Triangle and in other states.

This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include "Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!" Films will include Disney's Ethics in the Computer Age and more. This showing is an all ages, public event that is part of a series of monthly shows held at [http://kingsbarcade.com/ Kings Barcade], but the event has been scheduled and themed with the Code4Lib crowd in mind.

'''When:''' Doors open at 7:30 PM.

'''Where:''' Located two blocks from the Sheraton, Kings is a 250-capacity live music venue with a full bar and several local beers on tap. Kings is directly connected with the [http://neptunesparlour.com/ Neptunes Parlour], a cocktail lounge with classic arcade games, pinball, and nightly DJ's. The new [http://garlandraleigh.com/ Garland] Indian restaurant, operated by the same owners, is also downstairs.

'''Cost:''' The event is free with a suggested $5 donation.

'''Please add your name to the list below if you would like to attend so that we can inform the organizers about the level of interest:'''

* Steve Morris
*Laurie Lee Moses - this looks really fun!
* Heather Rayl - old education films AND Indian food??! What more could a girl want?
* Anna Headley
* Ian Walls
* Kevin Clarke

[[Category:Code4Lib2014]]

Code4Lib 2014 Conference Planning Volunteers

2013-11-22T21:51:53Z

Ksclarke: Changing from O'Reilly to Manning since Shaun contacted O'Reilly

= Code4Lib 2014 Committees =

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. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We hope to include at least one local person on each committee.

A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.

The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).

== Book Give-Away Committee ==

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.

Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.

* Kevin S. Clarke (Manning) and general wrangling (nominated as lead)
* Michael B. Klein (Pragmatic) and winner-picker app
* Sarah Shealy (Packt) and general wrangling if/when needed
* Shaun Ellis (Rosenfeld Media and O'Reilly eBooks)

Current Status:
* O'Reilly is also offering a free ebook to all attendees. This is in the form of a printed voucher that should be bundled with the t-shirt and other swag. Shaun Ellis is responsible for the printing of the vouchers.
* Rosenfeld Media is shipping a number of giveaway titles directly to Tim McGeary a couple weeks before the conference.

Shaun also mentioned that we have a prospectus this year that would be great to send along with our requests to the publishers. You can find it at: http://code4lib.org/files/Code4LibProspectus.pdf

== Keynote Speakers Committee ==

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.

Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013 
Keynote speaker voting - September 9, 2013 - September 20, 2013 
Have speakers finalized by November 15, 2013

* Jason Casden (NCSU) -- lead
* Tom Johnson (Johnson.tom@gmail.com)
* Bret Davidson (NCSU)
* Jeff Campbell (UNC)
* Joyce Chapman (State Library of NC)
* Dre (NCSU)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

* Kevin S. Clarke
* Kevin Beswick (NCSU)
* Yan Wang (NCCU)
* Kelly Leong (Duke)
* Dre (NCSU)

== Pre-conference Committee ==

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.

Call for pre-conf proposals -- October 14, 2013 
Deadline for pre-conf proposals -- December 6, 2013 
Finalize pre-confs before registration opens -- January 3, 2014 
Send rosters to pre-conf organizers -- by February 21, 2014

* Adam Constabaris (NCSU) -- nominated as lead
* Tim Shearer (UNC)
* Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

Call for talk proposals -- October 14 - November 8, 2013 
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013 
Voting on talks -- November 18, 203 - December 6, 2013 
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013 
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!) 
Post final program schedule with talks - January 13, 2014

* Tom Johnson (Johnson.tom@gmail.com) -- lead
* Kevin Beswick (NCSU)
* Ranti Junus (ranti.junus@gmail.com)
* Roy Tennant (OCLC)
* Trevor Thornton (hellotrevorthornton@gmail.com)
* Lucas Mak (makw@mail.lib.msu.edu)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)
* Tod Olson (tod at uchicago dot edu)

== Scholarships Committee ==

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.

Call for applicants -- November 18, 2013 - December 13, 2013 
Determine winners -- December 14, 2014 - January 5, 2014 
Notify winners -- January 6, 2014 (must be before registration)

* Jason Ronallo (NCSU) -- lead
* Cory Lown (NCSU)
* Bohyun Kim (FIU)
* Santi Thompson (University of Houston) sathompson3@uh.edu
* Sarah Shealy (sarah.shealy@outlook.com)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Jason Raitz
* Rosalyn Metz
* Dre
* Becky Yoose
* Bohyun Kim

== Sponsorships Committee ==

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.

* Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)
* Roy Tennant (OCLC)
* Shaun Ellis (shaune@princeton.edu)
* Robert H. McDonald (Indiana)
* Sean Chen (Duke)
* Thomas Dowling (Wake Forest)
* Will Sexton (Duke)
* Jeff Campbell (UNC)
* Brett Bonfield (Collingswood Public)

== Streaming Video Committee ==

This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.

Work with local team to get solid A/V estimates by late November 2013 to use for final budget.

- Francis Kayiwa
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)

== T-Shirt Committee ==

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. User sizes and preferences will be obtained as part of the registration process.

Call for T-shirt designs - December 2, 2014 - January 3, 2014 
Voting on T-shirt designs - January 13, 2014 - January 24, 2014 
Get bids based on sizes and design - January 27, 2014 - February 14, 2014 
Order t-shirts by February 17, 2014

*Charlie Morris (NCSU) -- lead
*Josh Wilson, State Library of NC (joshwilsonnc at gmail)

== Voting Activities Committee ==

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.

*Adam Constabaris (NCSU)

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Kevin S. Clarke
* Dre
* Ranti Junus
* [[User:LauraAkerman|Laura Akerman]], liblna@emory.edu

== Wifi / Electrical / IRC Committee==

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.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org
* [[User:RileyChilds|Riley Childs]], Riley@TFSGEO.com

This is a newly proposed committee.

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2014]]

Code4Lib 2014 Conference Planning Volunteers

2013-11-22T21:46:31Z

Ksclarke: /* Book Give-Away Committee */

= Code4Lib 2014 Committees =

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. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We hope to include at least one local person on each committee.

A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.

The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).

== Book Give-Away Committee ==

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.

Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.

* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)
* Michael B. Klein (Pragmatic) and winner-picker app
* Sarah Shealy (Packt) and general wrangling if/when needed
* Shaun Ellis (Rosenfeld Media and O'Reilly eBooks)

Current Status:
* O'Reilly is also offering a free ebook to all attendees. This is in the form of a printed voucher that should be bundled with the t-shirt and other swag. Shaun Ellis is responsible for the printing of the vouchers.
* Rosenfeld Media is shipping a number of giveaway titles directly to Tim McGeary a couple weeks before the conference.

Shaun also mentioned that we have a prospectus this year that would be great to send along with our requests to the publishers. You can find it at: http://code4lib.org/files/Code4LibProspectus.pdf

== Keynote Speakers Committee ==

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.

Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013 
Keynote speaker voting - September 9, 2013 - September 20, 2013 
Have speakers finalized by November 15, 2013

* Jason Casden (NCSU) -- lead
* Tom Johnson (Johnson.tom@gmail.com)
* Bret Davidson (NCSU)
* Jeff Campbell (UNC)
* Joyce Chapman (State Library of NC)
* Dre (NCSU)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

* Kevin S. Clarke
* Kevin Beswick (NCSU)
* Yan Wang (NCCU)
* Kelly Leong (Duke)
* Dre (NCSU)

== Pre-conference Committee ==

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.

Call for pre-conf proposals -- October 14, 2013 
Deadline for pre-conf proposals -- December 6, 2013 
Finalize pre-confs before registration opens -- January 3, 2014 
Send rosters to pre-conf organizers -- by February 21, 2014

* Adam Constabaris (NCSU) -- nominated as lead
* Tim Shearer (UNC)
* Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

Call for talk proposals -- October 14 - November 8, 2013 
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013 
Voting on talks -- November 18, 203 - December 6, 2013 
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013 
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!) 
Post final program schedule with talks - January 13, 2014

* Tom Johnson (Johnson.tom@gmail.com) -- lead
* Kevin Beswick (NCSU)
* Ranti Junus (ranti.junus@gmail.com)
* Roy Tennant (OCLC)
* Trevor Thornton (hellotrevorthornton@gmail.com)
* Lucas Mak (makw@mail.lib.msu.edu)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)
* Tod Olson (tod at uchicago dot edu)

== Scholarships Committee ==

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.

Call for applicants -- November 18, 2013 - December 13, 2013 
Determine winners -- December 14, 2014 - January 5, 2014 
Notify winners -- January 6, 2014 (must be before registration)

* Jason Ronallo (NCSU) -- lead
* Cory Lown (NCSU)
* Bohyun Kim (FIU)
* Santi Thompson (University of Houston) sathompson3@uh.edu
* Sarah Shealy (sarah.shealy@outlook.com)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Jason Raitz
* Rosalyn Metz
* Dre
* Becky Yoose
* Bohyun Kim

== Sponsorships Committee ==

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.

* Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)
* Roy Tennant (OCLC)
* Shaun Ellis (shaune@princeton.edu)
* Robert H. McDonald (Indiana)
* Sean Chen (Duke)
* Thomas Dowling (Wake Forest)
* Will Sexton (Duke)
* Jeff Campbell (UNC)
* Brett Bonfield (Collingswood Public)

== Streaming Video Committee ==

This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.

Work with local team to get solid A/V estimates by late November 2013 to use for final budget.

- Francis Kayiwa
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)

== T-Shirt Committee ==

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. User sizes and preferences will be obtained as part of the registration process.

Call for T-shirt designs - December 2, 2014 - January 3, 2014 
Voting on T-shirt designs - January 13, 2014 - January 24, 2014 
Get bids based on sizes and design - January 27, 2014 - February 14, 2014 
Order t-shirts by February 17, 2014

*Charlie Morris (NCSU) -- lead
*Josh Wilson, State Library of NC (joshwilsonnc at gmail)

== Voting Activities Committee ==

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.

*Adam Constabaris (NCSU)

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Kevin S. Clarke
* Dre
* Ranti Junus
* [[User:LauraAkerman|Laura Akerman]], liblna@emory.edu

== Wifi / Electrical / IRC Committee==

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.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org
* [[User:RileyChilds|Riley Childs]], Riley@TFSGEO.com

This is a newly proposed committee.

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2014]]

2014 preconference proposals

2013-11-19T15:08:23Z

Ksclarke: /* CLLAM @ code4lib */

==Code4Lib 2014 Pre-Conference Proposals==

Proposals will be accepted through December 6th, 2013.

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.

Pitch Format:

----

===NAME===
'''"Full-Day|Half-Day" [PREFERRED TIME]'''

Description

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

----

===Drupal4lib Sub-con Barcamp===
=====Full Day=====

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com

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.

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).

[[resources to help you learn drupal]]

====Interested in Attending:====

=====All Day=====
Renna Tuten

=====Morning=====

=====Afternoon=====

===Open Refine Hackfest===
'''"Half-Day"'''
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com

[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

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

----

===Responsive Design Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com
* Contact David Ward, University of Illinois, dh-ward@illinois.edu

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].

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu
* TA: Bess Sadler, Stanford University, bess@stanford.edu

This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Megan Kudzia
#Bret Davidson

===Blacklight Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Chris Beer, Stanford University, cabeer@stanford.edu

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.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===Managing Projects: Or I'm in charge, now what?===
'''Full-Day'''

Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu

This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good)

'''Interested in Attending'''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''

Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.

The schedule may include the following:

* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Bret Davidson

===CLLAM @ code4lib===
'''(Computational Linguistics for Libraries, Archives and Museums)'''

'''Full Day'''

Contacts:
* Douglas W. Oard (primary), oard (at) umd.edu
* Corey Harper, corey (dot) harper (at) nyu.edu
* Robert Sanderson, azaroth42 (at) gmail.com
* Robert Warren, rwarren (at) math.carleton.ca

We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers.

There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Devon Smith
# Kevin S. Clarke

[[:Category:Code4Lib2014]]

2014 preconference proposals

2013-11-19T15:07:48Z

Ksclarke: /* CLLAM @ code4lib */

2014 Invited Speakers Nominations

2013-08-06T20:58:57Z

Ksclarke: /* Victoria Stodden */

Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest.

==Cory Doctorow==
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow

==Jeri Ellsworth==

Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV
http://en.wikipedia.org/wiki/Jeri_Ellsworth

==Sarah Lacy==

Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy

==Andromeda Yelton==

Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/

==Victoria Stodden==

She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings, and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html

[[Category:Code4Lib2014]]

2014 Invited Speakers Nominations

2013-08-06T20:58:27Z

Ksclarke: /* Victoria Stodden */

Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest.

==Cory Doctorow==
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow

==Jeri Ellsworth==

Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV
http://en.wikipedia.org/wiki/Jeri_Ellsworth

==Sarah Lacy==

Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy

==Andromeda Yelton==

Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/

==Victoria Stodden==

She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html

[[Category:Code4Lib2014]]

Code4Lib 2014 Conference Planning Volunteers

2013-04-22T22:03:25Z

Ksclarke: /* Onsite Volunteer Committee */

Code4Lib 2014 Conference Planning Volunteers

2013-04-22T22:02:44Z

Ksclarke: /* Book Give-Away Committee */

Code4Lib 2014 Conference Planning Volunteers

2013-04-22T22:01:20Z

Ksclarke: /* Whatever Committee */

Code4Lib 2014 Conference Planning Volunteers

2013-04-22T22:00:16Z

Ksclarke: /* Whatever Committee */

Code4Lib 2014 Conference Planning Volunteers

2013-04-22T21:59:01Z

Ksclarke: /* Book Give-Away Committee */

2012-06-04T19:48:24Z

Ksclarke:

==Mentors==
We're looking to try out a mentorship program through the #code4lib channel on IRC Freenode. The idea is that experienced people who are willing to volunteer some time would provide 1-on-1 mentoring to those who would like to learn during an "Office hours" period, once a week. The idea is sort-of modelled on the Drupal project's [http://drupal.org/node/1242856 Core Office Hours]. If this sounds like something you'd like to contribute to, don't hesitate to add your name!

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Mentor name
! IRC name
! Social
! Willing to help with
! Office hours
|-
| [[User:Mdm|Matt McCollow]]
| mdm_
| [https://twitter.com/#!/mmccollow Twitter] [https://plus.google.com/109717224039901428149/ G+]
| Javascript
| Fridays, 1-2 pm EST
|-
| [http://ruebot.net Nick Ruest]
| ruebot
| [http://twitter.com/ruebot Twitter] [https://plus.google.com/107824412266039153440 G+]
| Islandora
| Fridays, 1-2 pm EST (pls ping in advance)
|-
| [http://jbfink.github.com John Fink]
| jbfink
| [http://twitter.com/adr t] [http://gplus.to/jbfink G+]
| git
| Fridays, 1-2pm EST or variable (ping in advance if you can)
|-
| [http://lackoftalent.org/michael/ Mike Giarlo]
| mjgiarlo
| [http://twitter.com/mjgiarlo t] [http://gplus.to/mjgiarlo G+] [http://facebook.com/mjgiarlo fb]
| Repository technology and architecture, Ruby, Git, Project Hydra, "Persistent identifiers"
| Fridays, 1-5 pm EST (pls ping in advance)
|-
| [http://kennison.name/ Brian Kennison]
| briankenn
|[https://plus.google.com/102025737199540421914/about G+]
| xslt
| Fridays, 1-2pm EST (let me know what works for you)
|-
| [http://github.com/tdonohue/ Tim Donohue]
| tdonohue
| [http://twitter.com/timdonohue Twitter]
| DSpace, repository technologies/integrations in general, SWORD protocol, digital preservation stuff
| [http://wiki.duraspace.org/display/~tdonohue/DSpace+Office+Hours Weds, 1-4pm ET in #duraspace channel on IRC Freenode]
|-
| [http://plus.google.com/106980687849423472398/about Kevin Clarke]
| ksclarke
| [https://plus.google.com/106980687849423472398/about G+]
| xml (xslt, xquery, etc.)
| Fridays, 1-2pm EST or variable (ping in advance if you can)
|-
|}
 

==Want to learn?==

If you would like to have mentor support on a specific topic, add your name below. There may be members of our community not listed above who would be willing help you.

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Name
! IRC name
! Social
! Looking to learn
|-
| Matt McCollow
| mdm_
| [https://twitter.com/#!/mmccollow Twitter] [https://plus.google.com/109717224039901428149/ G+]
| Ruby/Rails
|-
| [http://ruebot.net Nick Ruest]
| ruebot
| [http://twitter.com/ruebot Twitter] [https://plus.google.com/107824412266039153440 G+]
| Getting better with Solr
|-
| [http://jbfink.github.com John Fink]
| jbfink
| [http://twitter.com/adr t] [http://gplus.to/jbfink G+]
| Ruby/Rails
|-
| Max Klein
| maxoclc
| [https://twitter.com/#!/notconfusing twitter]
| Data Munging basics in a language you recommend, interfacing with MySQL in php
|}

2012 c4l2012 social activities

2012-02-09T00:03:48Z

Ksclarke: /* Wednesday, February 8, 2012 */

==Ideas==
* Woodinville distillery tour
** +1
* Seattle distillery tour
* Favorite local breweries
* Favorite local tea houses
* Favorite local used bookstores
* Visit hackerspace
** +1

==Planned events==

===Pre-Newcomer + Veterans dinner /drink-up Monday===
Early in town for pre-conference?
First time at code4lib?
Don't know anyone at code4lib?
Join fellow c4l newbies + 2nd + 3rd timers + veterans.
You will gain a bunch of new/veteran code4libbers in one night!
Sign up below (NO CAP). You can show up only for dinner or drinks or both!

But put your name so that we have a rough idea about the number of ppl who will show up =)

'''Plans'''
* When: Monday evening (2/6)
* For Dinner: Meet at 6PM (ish)at the hotel lobby
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite

Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian & Himalayan/Nepalese/Tibetan (vegetarian-friendly)]
0.8 miles 15 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - n/v leader
* Margaret Heller
* Sarah Johnston - n
* Andrea Schurr - n/v (2nd-timer)
* Jason Ronallo
* Karen Coombs - v
* Eric James
* Misty De Meo - n
* Keri Thompson - n
* Andreas Orphanides - v
* Tom Burton-West -v
* Keith Folsom - n
* Sam Meister - n
* Jen Weintraub - n
* Reservation made for 15. Bring cash if you can! =)

Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer
0.3 miles 8 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - n/v leader
* Lisa Kurt - n
* Margaret Heller
* Andrea Schurr - n/v (2nd-timer)
* Anoop Atre (Would love to if back from MS visit)
* Heather Pitts (maybe) - n
* Evviva Weinraub - Hope to join up if back from MS visit)
* Megan Banasek -n
* Misty De Meo (maybe) - n
* Keri Thompson (definitely)
* David Drexler (likely) - n
* Andreas Orphanides - v
* Rebecca Jones - n
* Chick Markley - v
* Ray Henry - n
* Jonathan Green (likely) - n
* Aaron Collier - n
* Tim Lepczyk - n

Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.

===Morning Run Tuesday===
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8

Link to the course map is at http://www.runningmap.com/?id=351428.

So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.

===Newcomer dinner Tuesday===
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.

Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!

'''Plans'''
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''
* Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]

''Guidelines:''
*Max of '''6''' per group
**Please, no waitlisting :(
*ID yourselves so we can get a good mix of new people and veterans in each group
**New folks - n
**c4l vets - v
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')
**Leader duties
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders
***Herd folks from hotel to restaurant (know where you're going!)

'''Restaurants'''

'''Restaurants within .25 miles of the hotel'''

[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)
* Martin Haye - n (2nd timer but it's been a ''long'' time)
<strike>* William Gunn - n</strike> - Sorry I must beg out, someone may want to take my spot.
* Rebecca Jones - n
* Chick Markley - v - leader
* Keri Thompson - n
* Andy Jackson - n
* Tom Burton-West -v
*'''capped at 6''' ''Reservation is at 6:30, I will be in lobby before walking over''

[http://oasiankitchen.com/ O'Asian Kitchen and Lounge] (Asian)

'''Restaurants between .25 miles and .5 miles of the hotel'''

[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)
We are meeting in the lobby of the hotel at 6pm.
* Ken Varnum - n
* Chad Nelson - n
* Ed Summers - v
* Tommy Ingulfsen - n
* Adam Wead - v or .5n
* Dan Coughlin - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://www.rockbottom.com/ The Rock Bottom Restaurant & Brewery] (American)
It seemed like all the others were full so I thought it start this in case anyone else is as crazy unprepared as I am. Since we have no reservations feel free to join.
* Jonathan Green (jonathan at discoverygarden dot ca) - n
* <strike> Ed Fugikawa ( ed AT coalliance DOT org ) </strike> - n ( sorry, work is getting in the way )
* Zinthia Briceno - n (@zbriceno)
* David Talley - n ( dwtalley AT uw DOT edu ) -- Where to meet? Hotel main entrance, 6pm?
* Patrick Berry - v (@pberry) -- Lobby at 6pm sounds perfect. I'm the short blonde guy. I guess I will "lead" our merry band of famished folk.
* Al Cornish - v
* Tom Keays - v
* Andrew Pasterfield - n ( deesnutz AT gmail punto com )
* '''Not Taking Reservations -- Come with us at your own risk'''

[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced) "Reservations made under Jason Clark at 6pm for 6 people. Meeting in hotel lobby around 5:45pm."
* Jason Clark - n/v leader
* Tamar Sadeh - n
* Kevin Clarke - v
* Gary Thompson - n
* Keith Folsom - n
* Sarah Park - n (my Seattle friend recommended this place!)

[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us. I'll be meeting in the hotel lobby at 6pm with some sort of sign. See you then!''
* Calvin Mah - (leader) - v
* David Isaak - n
* Aaron Collier - n
* Sean Hannan - v
* Joshua Gomez - v
* Charlie Morris - n
* '''capped at 6'''

[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean) Reservation for 6:15 -- Meet in hotel lobby at 6 -- I have short white hair and will be wearing a purple jacket.
* Jean Rainwater (leader) - v
* Kelley McGrath - n
* Lori Robare - n
* Emily Lynema - v
* Sarah Johnston - n
* Sam Meister - n
* '''capped at 6'''

[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection) ''Meet in the lobby at 6:15pm''
* Francis Kayiwa - (leader) "(get hold of me at first dot last name at goog as the date gets closer with your mobile)" v
* Michael Lindsey - v
* Dan Suchy - v
* David Drexler - n
* Laura Smart - n
* Heather Pitts - n
*'''capped at 6'''

[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food & they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''
* Joel Richard (richardjm AT si.edu) (leader) - v
* Margaret Heller - v
* Sibyl Schaefer (sschaefer AT rockarch . org) - v
* Tim Lepczyk (timlepczyk AT gmail.com) - n
* Ray Schwartz (schwartzr2@wpunj.edu) - v
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)
* '''capped at 6'''

[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''

*Becky Yoose (leader) - v
*Cynthia Ng - n
*Zoe Chao - v
*Stephanie Collett - n (2nd-timer)
*Bethany Nowviskie - n
* Ben Shum - n
*'''capped at 6'''

[http://www.panafricamarket.com/wp/ Pan Africa Restaurant & Bar] (Pan African)
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason

[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)

Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.

Has a jellyfish tank.

*Jason Ronallo (leader?) - v?
*Nettie Lagace - n
*Bohyun Kim - n/v (2nd-timer)
*Wendy Robertson - n
*Jennifer Bowen - n/v (3rd timer)
*James Stuart - n
*'''capped at six'''

'''Restaurants between .5 and 1 mile from hotel'''

[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]

* Andrew Nagy (leader) - v
* Cory Lown - v
* Tod Robbins - n
* Dennis Schafroth - n
*<strike> Tammy Allgood Wolf - n</strike> Sorry, I'm not feeling well and am going to cancel, if anyone wants my spot.
* Tim Shearer - v
* Tim Clarke - n
*'''capped at six'''

[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat). ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says "HI I'M MIKE GIARLO" or otherwise shouting his name or looking confused.''

* Mike Giarlo (leader) - v
* Carmen Mitchell - n
* Daniel Lovins - v
* Cary Gordon - v
* Declan Fleming - v
* Space available!!
* (CAPPED AT SIX!)

[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''

* Mark Matienzo (leader) - v
* Hillel Arnold - sophomore
* Devon Smith - v
* Derek Merleaux - sophmore
* Jennifer Weintraub - n
* Peter Green - n (2nd)

[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)

''Reservations for 6 at 7:00pm - Meet in lobby at 6:15''

* Ryan Wick (leader) - v
* Kate Zwaard - n
* Joe Atzberger - v
* Scott Fisher - n (2nd-timer)
* Anoop Atre - n
* Lisa Kurt - n
* '''capped at 6'''

[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list).

''No reservations for parties at Serious Pie...So, let's meet in the lobby at 6:30. Look for a guy wearing an 'Alma' sticker (me). Others out there...come and crash the 'capped at six' crowd heading to Serious Pie.''

* Christopher Spalding (leader) - v
* Robin Schaaf - n
* Jason Stirnaman - v
* Christina Morris - n
* Ray Henry - n
* Sean Purcell - n
* '''capped at 6'''

[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)

[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''

''We have reservations for 6 at 6:45.''

* Andreas Orphanides (leader) - v
* Mark Mounts - v
* Joe Montibello - n
* Justin Littman - n
* Ron Peterson
* Bobbi Fox - sophmore
* (CAPPED AT SIX!)
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before. Reservations for 6:15. Leaving from the hotel lobby at 5:45. ''If you dig Ruby, come to this. Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''
* Matt Zumwalt (leader) - v
* *Justin Coyne - n
* Misty De Meo - n
* Fumihiro Kato - n (2nd timer)
* Dan Brubaker Horst - n (3nd timer)
* Willy Mene - sophomore
* (CAPPED AT SIX)

[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)

[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)

[http://www.placepigalle-seattle.com/ Place Pigalle] (French)

[http://www.chezshea.com/ Chez Shea] (French)

[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)

[http://www.mezaseattle.com/index.html Meza] (Latin Fare)
Have reservations for 6.45. It's about a mile from hotel. 10min bus, 30 min walk. Meet in lobby @ 6 and we'll work out bus/walk/cab. -corey
* Tara Robertson - n
* Shawn Averkamp - sophomore
* Corey Harper - v (leader)
* Shaun Ellis - sophomore
* Jon Stroop - fifth year senior
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)
* '''capped at 6'''

[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)

[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)

[http://highlineseattle.com/ Highline] (Veg*n, bar)
* Jacob Reed - n
* Brian McBride - n

'''Restaurants more than 1 miles from the hotel'''

[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown.

[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good. So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do. Reservation at 6:45, meet in lobby at 6:15 with a plan of getting in the taxis at about 6:30. I'll be wearing a red and white Hawaiian shirt.

* Robert Haschart - leader - v third year
* Molly Pickral - n
* Erik Hetzner - 2nd c4l
* Paul Deschner -n (where should we meet?)

[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)

[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)

[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)

[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)

==="Get Lamp" viewing Tuesday (9 PM) ===

"Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom"

Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]

It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.

If there is additional interest, there may be another viewing this week.

===Morning Run Wednesday===
I (Ray Schwartz) will not be running on Wednesday. Though several others have said that they will meet at 7am in the Hotel Lobby. I would recommend to walk straight down west to the water front and turn right-heading north, following the pedestrian path. It goes on or some miles, so it is a good choice.

===Veg*n Dinner Wednesday===

We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.

*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front.

Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.

*James Stuart (leader)
*Sean Hannan
*Bohyun Kim
*Margaret Heller
*Laura Smart
*Sibyl Schaefer
*Cynthia Ng
*Andrea Shurr
*Eric James
*Birkin James Diana
*Sheree F
*Misty De Meo
*Keith Folsom
*14 (spots have opened up)
*15
*Reservation is for 15.

===Meat-Up Dinner Wednesday===

RIP Meat-Up. Going to Amazon for hurricanes.

(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)

===Evergreen/Koha and friends dinner Wednesday===
Put your name and any food limitations, we're meeting in the hotel lobby at 6pm.

Going to [http://www.pikebrewing.com/ The Pike Brewing Company]. They can't take a reservation for the dining room, but we can ofder food off the same menu in the bar area. Apparently there are tables that can be pushed together so we can all sit together. Let's do this. (Or, if you don't like this plan make another one :) I'll be offline this afternoon. --tara)

* Tara Robertson
* Chris Sharp
* Tod Robbins - n
* Ben Shum
* Anoop Atre - n
* Matt Carlson - n
* Luis Baquera - n
* Larry Baerveldt (someplace with beer, natch)
* David Drexler -n (if there's space)
* Wayne Schneider
* Joe Atzberger
* Jon Scott

===Archives MeetUp===
'''Wednesday, February 8, 8pm - Room 1001'''
Working in archives or special collections? Interested in practical and theoretical issues relating to archives and code? Join us for an informal get-together (we'll also be doing some prepping for the Craft Brew Drinkup).

===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===

'''Wednesday, February 8, 9 PM-ish - Room 1001''' (room sponsored by [http://yourmediashelf.com/ MediaShelf]

Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!

===UNC-Duke Basketball game, Wednesday (6 PM)===

'''Wednesday, February 8, 6:00 - [http://maps.google.com/maps?q=fox+bar+seattle&ll=47.614148,-122.334952&spn=0.006394,0.01929&oe=utf-8&client=firefox-a&fb=1&gl=us&hq=fox+bar&hnear=0x5490102c93e83355:0x102565466944d59a,Seattle,+WA&cid=0,0,17121402292050307829&t=m&z=16 FOX Sports Grill]'''

Looks like this may be the best local venue for watching the game. Meet in the lobby at 5:45, or just find us there. Out the lobby door, hang a left on 6th, five blocks, on the right.

===Dim Sum Lunch Thursday===

For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.

*Becky Yoose
* Declan Fleming - love me some Dim Sum!
* Adam Wead
* Heather Pitts
* Sibyl Schaefer
* Anoop Atre
* Dan Suchy
* Carmen Mitchell
* Tara Robertson
* Ray Schwartz
* Corey Harper
* Joshua Gomez
* Cary Gordon
* Mike Giarlo
* Joe Atzberger
* Dileshni Jayasinghe
* Ryan Wick
* Dennis Schafroth
* Mike Durbin
* Ben Shum
* Dan Chudnov
* Luis Baquera
* Jeremy Nelson

==Social Map - places of interest==
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]

==Seattle Events Feb 5-9==
===Saturday, February 4, 2012===
In case you are showing up really early.
* Belgianfest: http://www.washingtonbeer.com/belgianfest/
===Sunday, February 5, 2012===
* Clinton Fearon & The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/
* Addaura/Alda/Hallow, Comet
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216

===Monday, February 6, 2012===
* Silent Movie Mondays: Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.

===Tuesday, February 7, 2012===
* Lionize/Maylene & The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/
* The Pulltab Playboys/Rachel Lyn Harrington & The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/
* Twin Sister, Vera: http://theveraproject.org/shows/
* The Features, Chop Suey: http://www.chopsuey.com/
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/

===Wednesday, February 8, 2012===
* The Golden Blondes/The Jet Age/Mr. Drinx & The Pot Heads, Sunset: http://sunsettavern.com/
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map]) -- anyone have ideas about how to get there? -- It sounds like taxi is the best way to get there. Do we want to meet at the lobby at 5PM? +1
* YACHT/Secret Shopppers/Bobby Birdman, The Crocodile: http://thecrocodile.com/index.html

===Thursday, February 9, 2012===
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin
* The Jayhawks, Neptune Theater: http://stgpresents.org/
* Digital Leather, Comet
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html

===Ongoing Events===
* Seattle Art Museum: Tours are every Saturday & Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 & 1:30 pm.
* EMP: Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma

==Local events/places==
* Metrix Create Space
* Ada's Technical Books
* Northwest Outdoor Center
* Center for Wooden Boats
* Empty Sea Studios acoustic music

==Local Beer Places==
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&lng=-122.28263854980469&z=5 beer venues] maintained at Beermapping.com.
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&ie=UTF8&msa=0&msid=201783184139227541123.0004813e64758434cb054&source=embed&ll=47.558921,-122.106171&spn=0.442982,1.234589&z=10&source=embed map]) maintained by the Washington Beer Commission
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.

==See also==
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]

==Tour of the Seattle Public Library==

===Tuesday breakout session 3-4pm - max 20 ppl===

Meet by the coffee urns, leaving at 2:55pm (10% off at the gift shop if you mention that you are attending code4lib)

* Tara Robertson
* Bohyun Kim
* Shirley Lew
* Margaret Heller
* Ben Shum
* Chris Sharp
* Cynthia Ng
* Megan Banasek
* Chris Beer
* Peter Murray
* Bobbi Fox
* Joe Montibello
* Tim Lepczyk
* Mark Mounts
* Robin Dean
* Robert Haschart
* Zoe Chao
* Shawn Averkamp

More tour may come later. Stay tuned!

Jeff Christensen 206-387-4659

centaltours@spl.org

===Wednesday afternoon tour===
Tour on Tuesday was nice, but less of a "behind the scenes" experience than I'd hoped. The tour guide talked a bit about the building, architecture and some of the design aspects that worked (and didn't). Unfortunately the Wed tour will not include the automatic materials sorting room. Again, max 20 people.

Also, Wednesday needs a group wrangler.

Meet the Anne Repass, your tour guide by the gift shop, just inside the 5th Ave entrance.

* Anoop Atre
* Sean Chen
* Andrew Pasterfield
* Jacob Reed
* Brian McBride
* Calvin Mah
* Duncan Barth
* Molly Pickral
* Jean Rainwater
* Matt Critchlow
* Corey Harper
* Greg Schrank
* Luis Baquera
* Tamar Sadeh
* ernesto valencia
* Graham Trigg
* "due to a cancellation this could be you"
* Andrea Schurr
* "Vacant spot"
[[Category:Code4Lib2012]]