Code4Lib - User contributions [en]

Code4Lib 2023 Conference Committees

2022-11-30T21:37:42Z

Bess: Removing myself

= 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
* 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
* Kate Lynch - (katelynch@princeton.edu) - LPC 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
* 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]]

2023 Scholarship Documents

2022-11-14T21:01:07Z

Bess:

The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Committee re: funding available for awards. The committee connects scholarship winners with conference coordinators to plan travel and arrangements, and provides additional informational support leading up to and at the conference.

Meetings

Timeline and tasks

Call for applications

Disseminating the call

Application form

Application evaluation rubric

Contacting references

Applicant notifications

Scholarship announcement

Logistics emails

Buddy system

First-Timers' Guide for Scholarship Awardees

Post-conference feedback

Lessons learned

2023 Scholarship Documents

2022-11-14T21:00:31Z

Bess: Created page with "2018 Scholarship Documents The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Comm..."

2018 Scholarship Documents

The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Committee re: funding available for awards. The committee connects scholarship winners with conference coordinators to plan travel and arrangements, and provides additional informational support leading up to and at the conference.

Meetings

Timeline and tasks

Call for applications

Disseminating the call

Application form

Application evaluation rubric

Contacting references

Applicant notifications

Scholarship announcement

Logistics emails

Buddy system

First-Timers' Guide for Scholarship Awardees

Post-conference feedback

Lessons learned

2023 Keynote Speakers Nominations

2022-11-07T23:16:51Z

Bess: Edits to Dr. Grady's nomination

Nominations for Keynote speakers for the Code4Lib 2023 Conference are now being accepted. The conference will take place March 15-17, 2023 at Princeton University.

'''Nominations will close at midnight on November 29, 2022.'''

When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:

1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?

2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?

3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through unusual experience or background?

Please include a description and any relevant links. Please try to keep the list in alphabetical order.

We require the following information in your nomination for a candidate to act as keynote:
*Speaker’s full name
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information for candidate (email address)

The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Tyler Wade at tw8766@princeton.edu [mailto:tw8766@princeton.edu tw8766@princeton.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

[mailto:email_link.foo nominee's email address]

</pre>

__TOC__

== Dr. Siobahn Day Grady ==

Dr. Siobahn Grady is an Assistant Professor of Library and Information Sciences and the director of the Laboratory for Artificial Intelligence and Equity Research (LAIER[https://www.nccu.edu/slis/laboratory-artificial-intelligence-and-equity-research-laier]) at North Carolina Central University, the only ALA-Accredited Library School at an HBCU (Historically Black College or University). Dr. Grady's research is focused on using machine learning to identify sources of misinformation on social media, and on improving fault detection in autonomous vehicles. Dr. Grady is an IF/THEN Ambassador for the American Association for the Advancement of Science, a program which seeks to bring more women and minorities into hard sciences, technology, engineering and mathematics. Dr. Grady was the first woman to graduate with a computer science Ph.D. from N.C. A&T State University, and through her teaching, research, philanthropy and public speaking she is a passionate supporter of HBCUs and the students they serve. Code4Lib would benefit from learning about her work at LAIER and about her vision for minority girls' and women's futures in technology fields.

More Information about Dr. Grady Can be found at her website[https://siobahncday.com/].

[mailto:sday@nccu.edu Siobahn Grady]

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.

[mailto:jane@nowhere.foo janes_email_address]

Code4Lib 2023 Conference Committees

2022-10-06T17:33:38Z

Bess: Making it clear more people can volunteer for CSS

= 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
* Your Name Here - 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]]

Code4Lib 2023 Conference Committees

2022-10-06T17:28:23Z

Bess: Bess volunteering to coordinate Community Support Squad

= 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

== 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
* Your Name Here - 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]]

Code4Lib 2023 Conference Committees

2022-10-04T19:56:02Z

Bess: Added Bess to scholarship committee

= 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.sadler@princeton.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:

== 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
* Your Name Here - 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]]

2015 Preconference Proposals

2015-02-07T20:23:34Z

Bess: Remove Bess from Dive Into Hydra

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) || Presentations workshop (1: 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)
|-
| '''Broadway I & II (70)''' || Linked Data Workshop (56: Bringing their own projector) || Intro to Git & possibly beyond (40: Needs: projector/screen)
|-
| '''Broadway III & IV (70)''' || Visualizing Library Data (60: Needs: projector) || Intro to Docker (52)
|-
| '''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) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating - must be in this room - limit 20 attendants)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)
|-
| '''Studio (35)''' || (Empty) || 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) || DPLA API Workshop (34: Bringing their own projector)
|}

== 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 and the process of customizing the application.

'''TRAINING OUTLINE'''
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015

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

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

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.

'''[https://stanford.box.com/geohydra-code4lib2015 Slides]'''

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

====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

''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!

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].

====Replace yourself with a painfully complex bash script...or try Ansible====
Morning, Galleria III
* Chad Nelson, chad dot nelson @ 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.

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

===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]

====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 - sysadmin/developer
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
# Liza Harrell-Edge - end-user
# Jessica Venlet - end-user/archivist (can be there in the afternoon)
# Andrew Berger - "digital" archivist
# Bill Kelm - sysadmin
# Jeremy Floyd - end-user (archivist turned metadata librarian)
# Sara Amato (morning only) - end-user
# Julie Hardesty (afternoon only) - end-user (metadata librarian)

====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====
Full day, Parlor C
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''

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).

===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".

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

==== Dive into Hydra ====
Afternoon, Studio
* Justin Coyne, Data Curation Experts, justin@curationexperts.com
*

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.

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

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

''Readings''

'''Case Study 1: The Healthcare.gov rollout'''

* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries (The Verge): Thanks a lot, healthcare.gov]

* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]

* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]

'''Case Study 2: The Challenger disaster'''

* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.

* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]

* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]
* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]

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

[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.

==== 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?

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

[[Category:Code4Lib2015]]

2015 During the Conference Volunteers

2015-01-16T00:35:40Z

Bess: Let's use "helpers" instead of "evangelists"

code4lib 2015 During the Conference Volunteers



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

== IRC Helpers ==
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.

== 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

* Mx Matienzo (anarchivist)

==Registration Desk Volunteers==

'''Monday'''

'''Tuesday'''

'''Wednesday'''

==MCs==

'''Tuesday AM'''

'''Tuesday PM'''

'''Wednesday AM'''
*Becky, destroyer of last names, singer of badly adapted show tunes

'''Wednesday PM'''

'''Thursday AM'''

== 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'''

'''Tuesday PM'''

'''Wednesday AM'''

'''Wednesday PM'''

'''Thursday AM'''

== Raffles ==

== Whatever Else Needs to be Done ==

[[Category: Code4Lib2015]]

2015 Preconference Proposals

2014-11-04T00:19:38Z

Bess: fixed typo

== 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

=== Proposal formatting guidelines: ===

<pre>

=== Preconference Title: ===

One of:
'''"Full Day"'''
'''"Half Day [Morning]"'''
'''"Half Day [Afternoon]"'''

* Facilitator's name, affiliation, and email address
* Second facilitator's name, affiliation, email address, if second speaker

Abstract

''Interested in Attending''

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

#
#
#

</pre>

== Pre-conference Proposals ==

Post your ideas here!

=== 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
#
#

=== 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
#
#

===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
#

=== 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
#
#
#

=== Intro to Docker ===
'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, Kayiwa Consulting , 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''

1. Jim Hahn

=== 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''

=== 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 ===

One of:
'''"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
#
#

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

One of:
'''"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

''Placeholder for now - more information will be available before the proposal deadline''. More information about Write the Docs at http://docs.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'''
#
#
#

'''Afternoon'''
#
#
#

=== Linked Data Workshop ===

One of:
'''"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.

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

# Logan Cox
#
#

=== Archivematica for users and developers ===

One of:
'''"Full Day"'''

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com

Abstract:

This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.

In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration.

For the afternoon, we plan to bring the two groups together to discuss, share use cases, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessions.

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

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

#
#
#

=== 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

#
#
#

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

One of:
'''"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

#
#
#

[[Category:Code4Lib2015]]

2015 Prepared Talk Proposals

2014-11-04T00:07:31Z

Bess: submitting talk 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'''
==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 form 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

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

2014 preconference proposals

2013-11-05T17:21:56Z

Bess: /* Intro to Blacklight */

==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

===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

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

[[:Category:Code4Lib2014]]

2013 preconference proposals

2013-01-08T20:55:23Z

Bess: /* RailsBridge Intro to Ruby on Rails */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles
* Jason Casden
* Ryan Eby
* mark matienzo

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz
* James Van Mil
* Andrew Nagy

=== Intro to Blacklight CANCELLED ===

PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

Please add your name below and fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey].

'''I plan on attending:'''
# First and last name and email address
# John MacGillivray
# Jon Stroop - jstroop at princeton
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg
# Ian Walls
# Steven Villereal
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy
# Courtney Greene - crgreene at indiana dot edu
# Laney McGlohon
# Nancy Enneking
# Jason Raitz - jcraitz at ncsu dot edu
# Nick Cappadona
# Steven Marsden
# Linda Ballinger - ballingerl at newberry dot org
# Brendan Quinn
# Michael Levy - mlevy {at}ushmm {dot}org
# Michael North (m-north at northwestern dot edu)

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

'''I plan on attending:'''
* Erin Fahy
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James
* Sean Crowe
* Scott Hanrath
* Karen Coyle
* Charles Draper
* David Uspal

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe
* Karen coyle
* David Lacy
* mark matienzo
* David Uspal
* Emily Lynema
* Sean Chen

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon
* Nancy Enneking
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu
* Jason Raitz - jcraitz at ncsu dot edu
* Linda Ballinger - ballingerl at newberry dot org

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler (bess at stanford dot edu)
* Michael North
* Charles Draper
* Nick Cappadona

[[Category:Code4Lib2013]]

2013 preconference proposals

2013-01-08T20:51:17Z

Bess: /* Solr 4 In Depth */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles
* Jason Casden
* Ryan Eby
* mark matienzo

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz
* James Van Mil
* Andrew Nagy

=== Intro to Blacklight CANCELLED ===

PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

Please add your name below and fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey].

'''I plan on attending:'''
# First and last name
# John MacGillivray
# Jon Stroop - jstroop at princeton
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg
# Ian Walls
# Steven Villereal
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy
# Courtney Greene - crgreene at indiana dot edu
# Laney McGlohon
# Nancy Enneking
# Jason Raitz - jcraitz at ncsu dot edu
# Nick Cappadona
# Steven Marsden
# Linda Ballinger - ballingerl at newberry dot org
# Brendan Quinn
# Michael Levy - mlevy {at}ushmm {dot}org
# Michael North (m-north at northwestern dot edu)

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

'''I plan on attending:'''
* Erin Fahy
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James
* Sean Crowe
* Scott Hanrath
* Karen Coyle
* Charles Draper
* David Uspal

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe
* Karen coyle
* David Lacy
* mark matienzo
* David Uspal
* Emily Lynema
* Sean Chen

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon
* Nancy Enneking
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu
* Jason Raitz - jcraitz at ncsu dot edu
* Linda Ballinger - ballingerl at newberry dot org

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler (bess at stanford dot edu)
* Michael North
* Charles Draper
* Nick Cappadona

[[Category:Code4Lib2013]]

2013 preconference proposals

2013-01-07T18:59:43Z

Bess: /* RailsBridge Intro to Ruby on Rails */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles
* Jason Casden
* Ryan Eby
* mark matienzo

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz
* James Van Mil
* Andrew Nagy

=== Intro to Blacklight CANCELLED ===

PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

'''I plan on attending:'''
# First and last name
# John MacGillivray
# Jon Stroop - jstroop at princeton
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg
# Ian Walls
# Steven Villereal
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy
# Courtney Greene - crgreene at indiana dot edu

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

'''I plan on attending:'''
* Erin Fahy
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James
* Sean Crowe
* Scott Hanrath
* Karen Coyle
* Charles Draper
* David Uspal

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe
* Karen coyle
* David Lacy
* mark matienzo
* David Uspal
* Emily Lynema
* Sean Chen

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Linda Ballinger
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Brendan Quinn
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler
* Michael North
* Charles Draper

[[Category:Code4Lib2013]]

2013 preconference proposals

2013-01-07T18:58:47Z

Bess: /* Intro to Blacklight */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles
* Jason Casden
* Ryan Eby
* mark matienzo

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz
* James Van Mil
* Andrew Nagy

=== Intro to Blacklight CANCELLED ===

PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

'''I plan on attending:'''
# First and last name
# John MacGillivray
# Jon Stroop - jstroop at princeton
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg
# Ian Walls
# Steven Villereal
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy
# Courtney Greene - crgreene at indiana dot edu

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

'''I plan on attending:'''
* Erin Fahy
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James
* Sean Crowe
* Scott Hanrath
* Karen Coyle
* Charles Draper
* David Uspal

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe
* Karen coyle
* David Lacy
* mark matienzo
* David Uspal
* Emily Lynema
* Sean Chen

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Linda Ballinger
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Brendan Quinn
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler
* Michael North
* Charles Draper

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-12-14T00:23:37Z

Bess: /* Solr 4 In Depth */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* First and last name
* Esmé Cowles
* Jason Casden

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

'''I plan on attending:'''
* Linda Ballinger
* Terry Brady
* Shawn Kiewel
* First and last name

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

'''I plan on attending:'''
* First and last name
* Jon Stroop
* Christina Salazar
* Karen Coombs - coombsk{at}oclc{dot}org
* Becky Yoose
* Jeremy Morse
* Julia Bauder
* Chung Kang
* Karen Miller
* Betsy Coles
* Jay Luker
* Santi Thompson
* Sarah Dooley
* Brandon Dudley
* Ken Irwin
* Dennis Ogg
* Ian Walls
* Steven Villereal

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

'''I plan on attending:'''
* First and last name
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* First and last name
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* [[User:Kevenj|Keven Jeffery]]

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Linda Ballinger
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

'''I plan on attending:'''
* First and last name
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Brendan Quinn

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

'''I plan on attending:'''
* First and last name
* Becky Yoose
* Lisa Rabey

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler

[[Category:Code4Lib2013]]

2013 social activities

2012-12-12T22:15:01Z

Bess: /* Flying Trapeze */

== Ideas ==

* Game Night! Type of games might vary due to interest, could range from party games like Werewolf, Wits & Wagers, Telestrations, Taboo, Apples to Apples to perhaps more strategic games like De Vulgari Eloquentia or Eclipse. Jon Gorman is willing to bring some games, are you? Jon will try to send out an email soon to get some interest.
** yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.)
**danwho: I 'll bring the Cards Against Humanity set.
**escowles: I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc.
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 12.

== Planned Events ==

=== Newcomer Dinner ===

Placeholder - more to come

=== Veg*n Dinner ===

Let's have dinner at a veg*n-friendly place one night of the conference. All welcome.

Details later. Suggestions on where to eat near the conference hotel? Interested in coming or co-organizing? Contact Jason at jronallo@gmail.com.

=== Code4lib/Goose Island Brewing Pull Request ===
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM

More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]

=== Non-beery get together ===
'''When:''' Wednesday, 2/13, TBD (evening)

Contact: @dchud, @ranti, @yo_bj, @wendyrlibrarian

=== Flying Trapeze ===
'''When:''' Monday, 2/11, TBD

'''Contact:''' rosalynmetz at gmail dot com

No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib. There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well. If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class. If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.

Trapeze classes are $57, last 2 hours, and are limited to 10 people. Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1. If we can get enough people interested before then, we can buy out a whole class. If not it'll be first come, first serve (along with the general public).

If you're interested in signing up, feel free to add your name and contact info to the list below.

'''''Sign Up List'''''
# Jay Luker (first!)
# Bill McMillin
# Bess Sadler
#
#
#
#
#
#
#

== Social Map - Places of Interest==

https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0

== Local Events ==
== Local Food ==
== Local Drinks ==
==Chicago Events Feb 11-14==
===Monday February 11===
===Tuesday, February 12===
Field trip to the Read/Write Library (details to follow). 6-9 PM+
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will also invite friends from Code for America to hang out and talk civic data.

===Wednesday, February 13===
===Thursday, February 14===

[[Category:Code4Lib2013]]

Mentorship Program

2012-12-06T22:40:13Z

Bess: /* Mentee */

== Goals ==
* Bringing people together to build individual capacity

== Structure ==

== Platforms for communication ==

== Participants ==

=== Mentors ===
Bess Sadler - I currently have a couple of pro bono projects that would be good learning opportunities for someone interested in learning more about Blacklight, Ruby on Rails, Solr, museums, or libraries in Africa. I am also happy to be a mentor generally, and I'm open to suggestions about what form that might take.

=== Mentee ===

Bess Sadler - I have been a developer for Digital Humanities and Library software projects for over a decade, but I am relatively new to library management and administration and I would love to find a mentor with more experience than I have in those areas.

Mentorship Program

2012-12-06T22:33:33Z

Bess: /* Mentors */

2013 preconference proposals

2012-11-08T23:27:10Z

Bess: /* Intro to Blacklight */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

=== RailsBridge Intro to Ruby on Rails ===

* Jason Ronallo, NC State (jronallo at gmail.com)

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, version control with git, and participants will build a working Rails application.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-08T23:20:36Z

Bess: /* Half Day Afternoon */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

=== RailsBridge Intro to Ruby on Rails ===

* Jason Ronallo, NC State (jronallo at gmail.com)

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, version control with git, and participants will build a working Rails application.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-08T23:19:40Z

Bess: /* RailsBridge Intro to Ruby on Rails */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

=== RailsBridge Intro to Ruby on Rails ===

* Jason Ronallo, NC State (jronallo at gmail.com)

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, version control with git, and participants will build a working Rails application.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-08T23:18:56Z

Bess: /* Half Day Morning */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

=== RailsBridge Intro to Ruby on Rails ===

* Jason Ronallo, NC State (jronallo at gmail.com)

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, version control with git, and participants will build a working Rails application.

* Note: this workshop can be taken solo, or attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-08T23:11:28Z

Bess: /* Half Day Afternoon */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-08T23:10:53Z

Bess: /* Half Day Afternoon */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T21:56:13Z

Bess: /* Intro to Blacklight */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T21:28:49Z

Bess: /* Intro to Hydra */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State University Library (michael at psu.edu)
* Bess Sadler, Stanford University Library (bess at stanford.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T21:23:34Z

Bess: /* Intro to Blacklight */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Bess Sadler, Stanford University Library (bess at stanford.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:37:00Z

Bess: /* Intro to Hydra */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Bess Sadler, Stanford University Library (bess at stanford.edu)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:35:25Z

Bess: /* Intro to Blacklight */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:34:54Z

Bess: /* Intro to Blacklight */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Contact: Bess Sadler (bess at stanford.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:32:56Z

Bess: /* Half Day Morning */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Duration: half-day, morning
* Contact: Bess Sadler (bess at stanford.edu)
* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:32:31Z

Bess: /* Intro to Blacklight */

2013 preconference proposals

2012-11-07T18:32:08Z

Bess: /* Half Day Evening */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Blacklight ===

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Duration: half-day, morning
* Contact: Bess Sadler (bess at stanford.edu)
* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:31:35Z

Bess: /* Half Day Afternoon */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

=== Intro to Blacklight ===

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Duration: half-day, morning
* Contact: Bess Sadler (bess at stanford.edu)
* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-07T18:30:58Z

Bess: /* Intro to Blacklight */

2013 preconference proposals

2012-11-07T18:30:20Z

Bess: /* Solr 4 In Depth */

Proposals close ''Friday, November 9'' at 11:59pm ET.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day
* Contact: Chris Beer (cabeer at stanford.edu)

==Half Day Evening==

=== Solr 4 In Depth ===

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

=== Intro to Blacklight ===

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Duration: half-day, morning
* Contact: Bess Sadler (bess at stanford.edu)
* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

=== Intro to Hydra ===

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon
* Contact: Bess Sadler (bess at stanford.edu), Adam Wead (amsterdamos at gmail.com)

[[Category:Code4Lib2013]]

2013 talks proposals

2012-11-01T15:12:45Z

Bess: /* Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... */

'''Deadline has been extended by request due to the hurricane/storm.'''

Deadline for talk submission is ''Friday, November 9'' at 11:59pm ET. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.

Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:
* tools (some cool new software, software library or integration platform)
* specs (how to get the most out of some protocols, or proposals for new ones)
* challenges (one or more big problems we should collectively address)

The community will vote on proposals using the criteria of:
* usefulness
* newness
* geekiness
* uniqueness
* awesomeness

Please follow the formatting guidelines:

<pre>
== Talk Title ==

* Speaker's name, affiliation, and email address
* Second speaker's name, affiliation, email address, if applicable

Abstract of no more than 500 words.
</pre>

== Modernizing VuFind with Zend Framework 2 ==

* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu

When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.

== Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org

Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.

== Drupal 8 Preview — Symfony and Twig ==

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

Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.

It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.

Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.

== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==

* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu

Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, "Let's digitize these together and make them one big awesome project to support public urban history"? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of "grand ideas crushed by technological limitations" and "projects on the right track" to follow.

== ResCarta Tools building a standard format for audio archiving, discovery and display ==

* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org

The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit.

Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.

ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!!

You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old)

== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==

* Michael Doran, University of Texas at Arlington, doran@uta.edu

This presentation will use a seemingly simple data point, the "format" of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection.

I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session.

== Touch Kiosk 2: Piezoelectric Boogaloo ==

* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu

At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.

In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.

I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.

[1] http://journal.code4lib.org/articles/5832

== Wayfinding in a Cloud: Location Service for libraries ==

* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi

Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.

The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.

The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.

== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==

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

The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.
* Automatically inventory a collection of documents or images to be uploaded
* Generate a spreadsheet for metadata capture based on the inventory
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested
* Validate the contents of ingest folders prior to initiating the ingest to DSpace
* Present users with a simple, web-based form to initiate the batch ingest process

The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== Quality Assurance Reports for DSpace Collections ==

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

The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection

These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==

* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca

In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.

See article: http://journal.code4lib.org/articles/7470

== HTML5 Video Now! ==

* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu

Can you use HTML5 video now? Yes.

I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.

My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.

== Hybrid Archival Collections Using Blacklight and Hydra ==

* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org

At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.

Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.

== Making the Web Accessible through Solid Design ==

* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library & Archives

In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.

While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.

== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books & Much More ==

* Steven Marsden, Ryerson University Library & Archives, steven dot marsden at ryerson dot ca
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library & Archives

Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users.

The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.

The presentation will not only cover the technical aspects, but also the implementation and usability findings.

== De-sucking the Library User Experience ==

* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu

Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.

The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.

== Solr Testing Is Easy with Rspec-Solr Gem ==

* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu

How do you know if

* your idea for "left anchoring" searches actually works?
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?
* changes to your solrconfig file accomplish what you wanted without breaking anything else?

Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:

it "unstemmed author name Zare should precede stemmed variants" do
resp = solr_response(author_search_args('Zare').merge({'fl'=>'id,author_person_display', 'facet'=>false}))
resp.should include("author_person_display" => /\bZare\W/).in_each_of_first(3).documents
resp.should_not include("author_person_display" => /Zaring/).in_each_of_first(20).documents
end

it "Cyrillic searching should work: Восемьсoт семьдесят один день" do
   resp = solr_resp_doc_ids_only({'q'=>'Восемьсoт семьдесят один день'})
   resp.should include("9091779")
end

it "q of 'String quartets Parts' and variants should be plausible " do
   resp = solr_resp_doc_ids_only({'q'=>'String quartets Parts'})
   resp.should have_at_least(2000).documents
   resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'(String quartets Parts)'}))
   resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=>'"String quartets Parts"'}))
end

it "Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志" do
resp = solr_response({'q'=>'三國誌', 'fl'=>'id', 'facet'=>false})
resp.should have_at_least(240).documents
resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'三国志'}))
end

See
http://rubydoc.info/github/sul-dlss/rspec-solr/frames
https://github.com/sul-dlss/rspec-solr

and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:
https://github.com/sul-dlss/sw_index_tests

== Northwestern's Digital Image Library ==

*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu

At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL). DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:

*Build custom collection of images using drag-and-drop
*Re-order images within a collection using drag-and-drop
*Nest collections within other collections
*Create details/crops of images
*Zoom, rotate images
*Upload personal images
*Retrieve your own uploads and details from a collection
*Export a collection to a PowerPoint presentation
*Create a group of users and authorize access to your images
*Batch edit image metadata

Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.

== Two standards in a software (to say nothing of Normarc) ==

*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it

With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:
MARC21, Unimarc and Normarc. The main points of the presentation:

*Three MARC at MySQL level
*Three MARC at API level
*Three MARC at display
*Can I add a new format ?

== Future Friendly Web Design for Libraries ==

*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu

Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be "redesign") - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing.

So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything.

Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.

This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.

==BYU's discovery layer service aggregator==

*Curtis Thacker, Brigham Young University, curtis.thacker AT byu DOT edu

It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:

*filmfinder - a tool for browsing and searching films
*A custom book recommender service based on checkout data
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.
*Embedded floormaps
*A responsive web design
*Bing did-you-mean
*And many more.

I will demo the system, review the archtecture and talk about future plans.

==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==

* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu

Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:

* The ingest, search, and discovery functionality of the Hydra framework
* The powerful multimedia workflow management features of Opencast Matterhorn
* The flexible Engage audio/video player
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)

Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.

Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.

== The DH Curation Guide: Building a Community Resource ==

*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu

Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.

Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.

This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow.

== Solr Update ==

*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com

Solr is continually improving. Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features. It's tough for us all to keep up with the various versions and capabilities.

This talk will blaze through the highlights of new features and improvements in Solr 4 (and up). Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features. We will focus on the features library coders really need to know about.

== Reports for the People ==

*Kara Young, Keene State College, NH, kyoung1 at keene.edu
*Dana Clark, Keene State College, NH, dclark5 at keene.edu

Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward. In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty. Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier. Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.

The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis. The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation.
The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!

== Network Analyses of Library Catalog Data ==

* Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu
* Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu

Library collections are all too often like icebergs: The amount exposed on the surface is only a fraction of the actual amount of content, and we’d like to recommend relevant items from deep within the catalog to users. With the assistance of an XSEDE Allocation grant (http://xsede.org), we’ve used R to reconstitute anonymous circulation data from the University of Illinois’s library catalog into separate user transactions. The transaction data is incorporated into subject analyses that use XSEDE supercomputing resources to generate predictive network analyses and visualizations of subject areas searched by library users using Gephi (https://gephi.org/). The test data set for developing the subject analyses consisted of approximately 38,000 items from the Literatures and Languages Library that contained 110,000 headings and 130,620 transactions. We’re currently working on developing a recommender system within VuFind to display the results of these analyses.

== Pitfall! Working with Legacy Born Digital Materials in Special Collections ==

* Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com
* Mark A. Matienzo, Yale University Library, mark AT matienzo.org

Archives and special collections are being faced with a growing abundance of born digital material, as well as an abundance of many promising tools for managing them. However, one must consider the potential problems that can arise when approaching a collection containing legacy materials (from roughly the pre-internet era). Many of the tried and true, "best of breed" tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of "word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer" (Kirschenbaum, "Breaking <code>badflag</code>").

Our presentation will focus on some of the strange problems encountered and creative solutions devised by two digital archivists in the course of preserving, processing, and providing access to collections at their institutions. We'll be placing particular particular emphasis of the pitfalls and crocodiles we've learned to swing over safely, while collecting treasure in the process. We'll address working with CP/M disks in collections of authors' papers, reconstructing a multipart hard drive backup spread across floppy disks, and more.

== Project <s>foobar</s> FUBAR ==

* Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu

Be it mandated from Those In A Higher Pay Grade Than You or self-inflicted, many of us deal with managing major library-related technology projects [1]. It’s common nowadays to manage multiple technology projects, and generally external and internal issues can be planned for to minimize project timeline shifts and quality of deliverables. Life, however, has other plans for you, and all your major library technology infrastructure projects pile on top of each other at the same time. How do you and your staff survive a train wreck of technology projects and produce deliverables to project stakeholders without having to go into the library IT version of the United States Federal Witness Protection Program?

This session covers my experience with the collision of three major library technology projects - including a new institutional repository and an integrated library system migration - and how we dealt with external and internal factors, implemented damage control, and overall lessening the damage from the epic crash. You might laugh, you might cry, you will probably have flashbacks from previous projects, but you will come out of this session with a set of tools to use when you’re dealing with managing mission-critical projects.

[1] Past code4lib talks have covered specific project management strategies, such as Agile, for application development. I will be focusing on and discussing general project management practices in relation to various library technology projects, many of which these strategies include in their own structures.

== Implementing RFID in an Academic Library ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

Coastal Carolina University’s Kimbel Library recently implemented RFID to increase security, provide better inventory control over library materials and enable do-it-yourself patron services such as self checkout.

I’ll give a quick overview of RFID and the components involved and then will talk about how our library utilized the technology. It takes a lot of research, time, money and not too little resourcefulness to make your library RFID-ready. I’ll show how we developed our project timeline, how we assessed and evaluated vendors and how we navigated the bid process. I’ll also talk about hardware and software installation, configuration and troubleshooting and will discuss our book and media collection encoding process.

We encountered myriad issues with our vendor, the hardware and the software. Would we do it all over again? Should your library consider RFID? Caveats abound...

== Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

The Kimbel Library Intranet is coded in Drupal 7, and was created to increase staff communication and store documentation. This presentation will contain an overview of our intranet project, including the modules we used, implementation issues, and possible directions in future development phases. I won’t forget to talk about the slew of tasty development issues we faced, including dealing with our university IT department, user buy-in, site navigation, user roles, project management, training and mobile modules (or the lack thereof). And some other fun (mostly) true anecdotes will surely be shared.

The main functions of Phase I of this project were to increase communication across departments and committees, facilitate project management and revise the library's shared drive. Another important function of this first phase was to host mission-critical documentation such as strategic goals, policies and procedures. Phase II of this project will focus on porting employee tasks into the centralized intranet environment. This development phase, which aims to replicate and automate the bulk of staff workflows within a content management system, will be a huge undertaking.

We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?

== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==

* Naomi Dushay, Stanford University Library, ndushay@stanford.edu
* Bess Sadler, Stanford University Library, bess@stanford.edu

Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off?

== How to be an effective evangelist for your open source project ==

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

The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier.

[[Category:Code4Lib2013]]

A Guide for the Perplexed

2011-05-06T19:47:31Z

Bess: /* People with a background in libraries / archives / museums */

= A guide for the perplexed =

== What is this? ==

Very few people plan to have a career in library technology. Maybe you have a background in traditional librarianship, but you'd like to be a systems librarian. Maybe you're an experienced programmer, but you're having trouble learning about library specific standards. This guide is a starting point for you. It will not attempt to be a replacement for university-level education in either library studies or computer science, but it will give you a general sense of the areas of technology that are used by libraries, background knowledge you'll need in order to work effectively in these areas, and advice and ideas on how to acquire necessary skills.

Advice in this guide should focus on concrete, immediately applicable skills whenever possible. This document should be a curriculum guide, not a textbook, so before attempting to write an article on a broadly applicable subject, check to see if wikipedia has one to which you could link and contribute.

Samples of Curriculums:

* [https://docs.google.com/document/d/122dK_3JpK5URdNBfRG_CPiwP9m_Imc1gD3vnPV-C4Mo/edit?hl=en&authkey=CK-a5M8K Google Doc for Hydra Curriculum]
* [http://interact.webstandards.org/curriculum WaSP InterACT Curriculum.]

== Who is this for? ==

=== People with a background in libraries / archives / museums ===

Learning about technology can be intimidating, especially when it is a departure from the areas you're used to studying. You may have been put into a situation where you are responsible for managing or completing a technology project, but you don't understand the technology involved, and you're having a hard time finding information about it. Don't worry, this is surprisingly common and you are not alone. Many of the members of the code4lib community are self-taught, and we're here to help.

Here's a good blog post aimed at people in this category: [http://onebiglibrary.net/story/advice-to-a-library-school-student Advice to a Library School Student by Dan Chudnov]

=== People with a background in technology / computer science ===

== Why is it necessary? ==

== Broad areas of library technology ==

=== Data Formats ===

* [http://wiki.code4lib.org/index.php/Working_with_MaRC Working with MaRC]

=== Integrated Library Systems ===

=== Discovery Interfaces ===
* Blacklight http://projectblacklight.org
* Vufind

=== Article Databases ===

=== Institutional Repositories ===

=== EAD / Archival Finding Aids ===

=== Web Archiving ===

== Specific Technologies ==

=== Solr ===
http://lucene.apache.org/solr
searches at http://lucidimagination.com include wikis, email lists, etc.

=== Lucene ===
http://lucene.apache.org
searches at http://lucidimagination.com include wikis, email lists, etc.

=== Git & Distributed Version Control ===

[http://git-scm.com/| Main Git Website]

[http://github.com/| GitHub]

=== Ruby on Rails (Blacklight, Hydra) ===

A Guide for the Perplexed

2011-02-09T15:44:05Z

Bess:

= A guide for the perplexed =

== What is this? ==

Very few people plan to have a career in library technology. Maybe you have a background in traditional librarianship, but you'd like to be a systems librarian. Maybe you're an experienced programmer, but you're having trouble learning about library specific standards. This guide is a starting point for you. It will not attempt to be a replacement for university-level education in either library studies or computer science, but it will give you a general sense of the areas of technology that are used by libraries, background knowledge you'll need in order to work effectively in these areas, and advice and ideas on how to acquire necessary skills.

Advice in this guide should focus on concrete, immediately applicable skills whenever possible. This document should be a curriculum guide, not a textbook, so before attempting to write an article on a broadly applicable subject, check to see if wikipedia has one to which you could link and contribute.

Samples of Curriculums:

* [https://docs.google.com/document/d/122dK_3JpK5URdNBfRG_CPiwP9m_Imc1gD3vnPV-C4Mo/edit?hl=en&authkey=CK-a5M8K Google Doc for Hydra Curriculum]
* [http://interact.webstandards.org/curriculum WaSP InterACT Curriculum.]

== Who is this for? ==

=== People with a background in libraries / archives / museums ===

Learning about technology can be intimidating, especially when it is a departure from the areas you're used to studying. You may have been put into a situation where you are responsible for managing or completing a technology project, but you don't understand the technology involved, and you're having a hard time finding information about it. Don't worry, this is surprisingly common and you are not alone. Many of the members of the code4lib community are self-taught, and we're here to help.

=== People with a background in technology / computer science ===

== Why is it necessary? ==

== Broad areas of library technology ==

=== Data Formats ===

* [http://wiki.code4lib.org/index.php/Working_with_MaRC| Working with MaRC]

=== Integrated Library Systems ===

=== Discovery Interfaces ===

=== Article Databases ===

=== Institutional Repositories ===

=== EAD / Archival Finding Aids ===

=== Web Archiving ===

2011 Lightning Talks Signup

2011-02-09T15:39:40Z

Bess:

'''Sign up for Lightning Talks Now!!'''

Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing.

Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:

Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.

Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.

Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.

You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk]

Note to presenters: Projector resolution is 1024x768

'''Tuesday, 4-5pm, Alumni Hall [12 slots]'''
# 5 minutes of OPAC stats that might surprise you, or maybe not. -- Bill Dueber
# [http://socialarchive.iath.virginia.edu/ Social Networks and Archival Context] [http://socialarchive.iath.virginia.edu/xtf/search Prototype] [http://btingle.bitbucket.org/c4l11/ slides]- Brian Tingle
# AjaxyDialog jquery-ui widget - jonathan rochkind
# 2 little EAD gems - Jason Ronallo http://github.com/jronallo
# LYRASIS' Open Source Software Efforts - [[User:DataGazetteer|Peter Murray]]
# [http://www.hathitrust.org/blogs HathiTrust Large Scale Search] update. - Tom Burton-West
# UC San Diego Mobile Apps - Esme Cowles
# Blacklight and Hydra at the Rock and Roll Hall of Fame - Adam Wead
# Open data and the Biodiversity Heritage Library experience - Trish Rose-Sandler
# [http://iss.ndl.go.jp/?locale=en NDL Search] [http://www.slideshare.net/nabeta/ndl-search-beta-6856823 slides]- Kosuke Tanabe
# Making integrated search system which your choice - primo central index or summon? - Takanori Hayashi

Tuesday's actual order:
# 5 minutes of OPAC stats that might surprise you, or maybe not. -- Bill Dueber
# [http://socialarchive.iath.virginia.edu/ Social Networks and Archival Context] [http://socialarchive.iath.virginia.edu/xtf/search Prototype] [http://btingle.bitbucket.org/c4l11/ slides]- Brian Tingle
# AjaxyDialog jquery-ui widget jonathan rochkind
# 2 little EAD gems - Jason Ronallo
# LYRASIS' Open Source Software Efforts - [[User:DataGazetteer|Peter Murray]]
# UC San Diego Mobile Apps - Esme Cowles
# Blacklight and Hydra at the Rock and Roll Hall of Fame - Adam Wead
# [http://www.hathitrust.org/blogs HathiTrust Large Scale Search] update. - Tom Burton-West
# Open data and the Biodiversity Heritage Library experience - Trish Rose-Sandler
# [http://iss.ndl.go.jp/?locale=en NDL Search] [http://www.slideshare.net/nabeta/ndl-search-beta-6856823 slides] - Kosuke Tanabe
# Making integrated search system which your choice - primo central index or summon? - Takanori Hayashi

'''Wednesday, 3:50-5pm, Alumni Hall [14 slots]'''
# Theodor Tolstoy - Experiences from implementing Ebsco Discovery Service through their Web Service.
# Edward Corrado - Small Scale Koha
# Andreas Orphanides - Touch screen kiosk development and/or usage analysis, maybe with some nifty heatmaps and stuff
# Eric Lease Morgan - Beyond full-text indexing in "next-generation" library catalogs
# Ryan Eby - Does anyone else hate this shit? (metadata and what not)
# Cory Lown - Mobile Web Apps for Library Exhibits - [http://www.lib.ncsu.edu/m/exhibits/4h/ Exhibit Page] - [http://www.lib.ncsu.edu/dli/projects/mobileexhibits/ Project Page]
# Stephen Meyer - Better Subject Browsing
# Summa/Summon: Something, something (merging search results) - Mads Villadsen, Toke Eskildsen
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : having oracle & solr working together. Aurélien Charot, [http://www.abes.fr ABES]
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : edit and xml into a form. Olivier Martinez, [http://www.abes.fr ABES]
# Haruki Ono - Two Engineering Projects of LIS at Tsukuba in Japan: [http://www.shizuku.ne.jp/ Project Shizuku] and [http://ustream.tv/channel/l1gp Project Lie]
# Tracy Seneca. (Web) Archiving the oil spill – UI changes driven by context
# Hillel Arnold - Asian/Pacific American Documentary Heritage Archives Survey
# Bess Sadler - let's build a code4lib curriculum
# Ben Anderson - write a service for the MST. (I already did a 20 min presentation. Can I do a lightning as well?) (No, please don't. One of the tenets of code4lib is to give more people a chance to speak.)

[[Category:Code4Lib2011]]

A Guide for the Perplexed

2010-11-01T01:04:35Z

Bess: /* People with a background in libraries / archives / museums */

A Guide for the Perplexed

2010-11-01T01:03:23Z

Bess: /* People with a background in libraries / archives / museums */

A Guide for the Perplexed

2010-11-01T01:03:02Z

Bess: /* People with a background in libraries / archives / museums */

A Guide for the Perplexed

2010-11-01T01:01:34Z

Bess: /* People with a background in libraries / archives / museums */

A Guide for the Perplexed

2010-11-01T00:53:31Z

Bess: New page: = A guide for the perplexed = == What is this? == Very few people plan to have a career in library technology. Maybe you have a background in traditional librarianship, but you'd like t...

Main Page

2010-11-01T00:40:00Z

Bess: /* About Code4Lib */

__NOTOC__
= Code4Lib Wiki =

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MaRC]]
* [[Rogue]] - principles for standards creation

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

== Code4Lib 2011 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''

* [[2011_nominations_list|Keynote Nominations]] and [http://vote.code4lib.org/election/index/16 Vote]
* [[2011talkscall_Call_for_Submissions]] - sign up to give a prepared talk
* [[2011_Preconference_Proposals]] - sign up to present a day long or half-day preconference
* [[2011 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2011 Breakout Sessions]] - suggest a breakout here
* '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

== Earlier Conferences and events ==

== Code4libcon 2010 ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]

=== Deals ===
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!

=== Asheville planning ===
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Working with MARC

2010-03-13T06:33:13Z

Bess: /* Java */

== Working with MaRC ==

MaRC stands for Machine Readable Cataloging, and many folks in the code4lib community find themselves working with marc records at some point. This page is meant to be a round-up of the tools for working with marc. If you want a general introduction to the standard, [http://en.wikipedia.org/wiki/MARC_standards the wikipedia article] is a good place to start.

=== Desktop tools ===
[http://people.oregonstate.edu/~reeset/marcedit/html/index.php MarcEdit]

=== Getting Sample Data ===

One common question is where to get sample marc records for testing or playing around with. If you work at a library, chances are good that you can get some records out of your ILS (go ask your systems librarian if you don't know how to do this yourself). If you don't work in a library, you can get marc records from the internet archive at [http://www.archive.org/details/marcrecords http://www.archive.org/details/marcrecords].

There is a nascent movement within the code4lib community to establish a test set of problematic marc records, especially records that are representative of the kinds of weirdness that is encountered in real libraries. It is hoped that this could eventually become a test corpus against which to run various marc processing implementations. For more information, watch [http://www.archive.org/details/MARCTHULU Simon Spero's excellent talk from Code4LibCon 2010].

=== Searching and Indexing Systems ===

==== Solr ====

[http://code.google.com/p/solrmarc/ solrmarc]

==== Zebra ====

[[Getting Started with Zebra]] - indexing and searching MARC records

=== Programming libraries ===

==== Java ====

[http://marc4j.tigris.org/ marc4j]

==== Perl ====

There are quite a few options for manipulating MaRC with perl. You can find many of them at CPAN at [http://search.cpan.org/search?query=marc&mode=all http://search.cpan.org/search?query=marc&mode=all]

==== PHP ====

[http://pear.php.net/package/File_MARC/ File_MARC]

==== Python ====

[http://pypi.python.org/pypi/pymarc pymarc]

==== Ruby ====

[[ruby-marc]] - some notes and recipes for processing MARC files in ruby

Working with MARC

2010-03-13T06:32:18Z

Bess: /* Python */

== Working with MaRC ==

MaRC stands for Machine Readable Cataloging, and many folks in the code4lib community find themselves working with marc records at some point. This page is meant to be a round-up of the tools for working with marc. If you want a general introduction to the standard, [http://en.wikipedia.org/wiki/MARC_standards the wikipedia article] is a good place to start.

=== Desktop tools ===
[http://people.oregonstate.edu/~reeset/marcedit/html/index.php MarcEdit]

=== Getting Sample Data ===

One common question is where to get sample marc records for testing or playing around with. If you work at a library, chances are good that you can get some records out of your ILS (go ask your systems librarian if you don't know how to do this yourself). If you don't work in a library, you can get marc records from the internet archive at [http://www.archive.org/details/marcrecords http://www.archive.org/details/marcrecords].

There is a nascent movement within the code4lib community to establish a test set of problematic marc records, especially records that are representative of the kinds of weirdness that is encountered in real libraries. It is hoped that this could eventually become a test corpus against which to run various marc processing implementations. For more information, watch [http://www.archive.org/details/MARCTHULU Simon Spero's excellent talk from Code4LibCon 2010].

=== Searching and Indexing Systems ===

==== Solr ====

[http://code.google.com/p/solrmarc/ solrmarc]

==== Zebra ====

[[Getting Started with Zebra]] - indexing and searching MARC records

=== Programming libraries ===

==== Java ====

==== Perl ====

There are quite a few options for manipulating MaRC with perl. You can find many of them at CPAN at [http://search.cpan.org/search?query=marc&mode=all http://search.cpan.org/search?query=marc&mode=all]

==== PHP ====

[http://pear.php.net/package/File_MARC/ File_MARC]

==== Python ====

[http://pypi.python.org/pypi/pymarc pymarc]

==== Ruby ====

[[ruby-marc]] - some notes and recipes for processing MARC files in ruby