Code4Lib - User contributions [en]

BookRaffle

2020-04-03T19:16:32Z

JulieSwierczek: added part about printing certificates to hand out codes

=Raffle tool=
Kyle Bannerjee has a raffle tool here:http://raffle.alptown.com/

=Lessons Learned=
If you have too much stuff to give away, let winners select more than one prize.

It's useful to break up the giveaways into groups of three. This takes about 5-7 minutes, and still leaves time for other announcements at the podium.

At least two people should handle the raffle so that one person can call the names and the other person can handle prize distribution. Also, someone needs to note the names of the winners so they can be removed from the next raffle.

Timing is critical. Giveaways immediately after lunch go faster because most attendees come back to the room for the next session. Slots after a poster session or between lightning talks and breakout sessions are much slower, as many people choose to take a break and not return to the room. It is therefore necessary to call lots of names before selecting someone present in the room. Giveaways on the final day are avoided since attendance is lower that day.

If you have software codes or coupon codes as prizes, it can be helpful to print them onto individual certificates that can be handed out to winners.

For fun, have a sound tech add a drum roll.

In 2020, several publishers gave an ebook license or discount code for all attendees. It might be better to request more of those kinds of rewards from publishers and do fewer individuals prizes.

=Publishing and software companies=
Be sure to include companies in a "Giveaway Sponsors" section on the conference sponsorship page.

The following companies have contributed prizes:
*ALA Publishing
*APress
*Balsamiq
*CRC press
*Manning
*Morgan & Claypool
*No Starch Press
*Oxygen XML
*Pragmatic Programmers
*Rosenfeld Media

=Boilerplate=
A variation of the following was sent to each company:

I am writing on behalf of the code4lib {year} conference Book Giveaway Committee to request a contribution to give away at our annual conference. All conference attendees are included in the drawing for prizes.

code4lib (http://www.code4lib.org/) is a community of programmers and technologists who largely work for and with libraries. At our annual conference, we like to do multiple drawings for free books and software licenses. We would be grateful to have a few {books or licenses} to giveaway at the conference, which will be in {location} on {date}. {In some cases, it is helpful to suggest titles: A range of our participants would be interested in titles such as x, y, and z.}

We will gladly include the {company} name in our acknowledgement of supporters for the giveaways; please let me know how you would like the name to be written.

If you have any questions or if you need more information, please don’t hesitate to contact me.

[[Category:Conferences]]

BookRaffle

2020-04-03T19:12:25Z

JulieSwierczek: added Kyle's raffle tool

=Raffle tool=
Kyle Bannerjee has a raffle tool here:http://raffle.alptown.com/

=Lessons Learned=
If you have too much stuff to give away, let winners select more than one prize.

It's useful to break up the giveaways into groups of three. This takes about 5-7 minutes, and still leaves time for other announcements at the podium.

At least two people should handle the raffle so that one person can call the names and the other person can handle prize distribution. Also, someone needs to note the names of the winners so they can be removed from the next raffle.

Timing is critical. Giveaways immediately after lunch go faster because most attendees come back to the room for the next session. Slots after a poster session or between lightning talks and breakout sessions are much slower, as many people choose to take a break and not return to the room. It is therefore necessary to call lots of names before selecting someone present in the room. Giveaways on the final day are avoided since attendance is lower that day.

For fun, have a sound tech add a drum roll.

In 2020, several publishers gave an ebook license or discount code for all attendees. It might be better to request more of those kinds of rewards from publishers and do fewer individuals prizes.

=Publishing and software companies=
Be sure to include companies in a "Giveaway Sponsors" section on the conference sponsorship page.

The following companies have contributed prizes:
*ALA Publishing
*APress
*Balsamiq
*CRC press
*Manning
*Morgan & Claypool
*No Starch Press
*Oxygen XML
*Pragmatic Programmers
*Rosenfeld Media

=Boilerplate=
A variation of the following was sent to each company:

I am writing on behalf of the code4lib {year} conference Book Giveaway Committee to request a contribution to give away at our annual conference. All conference attendees are included in the drawing for prizes.

code4lib (http://www.code4lib.org/) is a community of programmers and technologists who largely work for and with libraries. At our annual conference, we like to do multiple drawings for free books and software licenses. We would be grateful to have a few {books or licenses} to giveaway at the conference, which will be in {location} on {date}. {In some cases, it is helpful to suggest titles: A range of our participants would be interested in titles such as x, y, and z.}

We will gladly include the {company} name in our acknowledgement of supporters for the giveaways; please let me know how you would like the name to be written.

If you have any questions or if you need more information, please don’t hesitate to contact me.

[[Category:Conferences]]

2020 Book Giveaway Documents

2020-04-03T19:10:52Z

JulieSwierczek: updated content to point people to the BookRaffle general page

[[User:JulieSwierczek|Julie Swierczek]] has a planning document in Google. If you join the committee, email Julie for access.

Notes from the committee were integrated into the [[BookRaffle|Book Raffle]] page.

How To Plan A Code4LibCon

2020-04-03T19:08:45Z

JulieSwierczek: added link to BookRaffle page

== General Process ==
* Apply to be a host; see also the page on [http://code4lib.org/conference/hosting Conference Hosting] at [http://code4lib.org code4lib.org]
** '''Identify venues''' for both the conference and the hotel (if different). Get some cost estimates from each. Make sure the hotel will give you a room block.
*** 2006/Corvallis: the campus provided the conference space at a low cost, and this made running the conference much more affordable.
*** 2016/Portland: we held everything in a single hotel and we had to acquire 2x the amount of sponsorship than what appears to be normal.
** '''Prepare a sample / generalized budget'''
*** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.
*** Get data from previous years to estimate minimums and maximums, and fill in as much as you can ahead of time.
*** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.
*** Also, when you get cost estimates, don't forget to include food costs.
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs.
** '''Consider using a conference planner'''
*** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.
*** Also consider using conference planning services from other entities. In 2013, Chicago used DLF services to handle registration. In 2014, NC used CONCENTRA services for all contract negotiation, fiscal activities, registration, and other conference planning and management services.
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]
* Invite the community to join committees
* Have a timeline
*[[Useful information from 2012]]

== Important Public Resources ==
* Past calls for host sites: [http://code4lib.org/node/275 2010] -
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]
* Sponsorship info (public)
* [http://code4lib.org/logo/ Logos]
* [http://code4lib.org/content/template-code4lib-20xx Template for the conference page on the main Code4Lib website] - This page is only visible to those who have a code4lib.org account. Once a host has been selected, please copy the template to a new page for that conference year.
* [[Code4Lib Conference Lessons Learned]]

== Important Private Resources ==
* Code4LibCon-hostsite listserv
* Budgets from previous years
* Sponsorship info (private)

== Committee List ==
* Local Planning Committee
* Accessibility Committee
* [[BookGiveawayCommittee|Book Giveaway Committee]]
* Childcare
* Documentation
* Keynote
* Onsite Volunteer
* Pre-conference
* [[ProgramCommittee|Program Committee]]
* [[ScholarshipCommittee|Gender Diversity & Minority Scholarship Committee]]
* Slack/IRC
* Social Activities
* [[SponsorshipCommittee|Sponsorship Committee]]
* Streaming Video
* [[T-ShirtCommittee|T-Shirt Committee]]
* [[Voting|Voting]]
* Whatever
* Wifi/Electrical
* Duty Officers

== Planning ==

=== Budgeting ===
* [[Conference_Financial_History_At_A_Glance]]
* private conlist has budget info

=== Hotels ===
* You will likely have to convince the conference hotel of the conference size and past room uptake as part of negotiating your contract. They may want to contact past conference hotels to get more info about actual uptake.
* 2014 -- Raleigh Downtown Sheraton
* IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.
* Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.
* prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012

TODO: get actual room uptake numbers into a chart here. (NB totals are only useful in the context of how many attendees there were.)

=== Wireless ===
* make sure VPN is allowed

TODO: put actual concurrent connections and bandwidth usage data numbers in a chart here. Note when problems were occurring to give context on whether these numbers were sufficient of insufficient.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

=== Policies ===
A record of [[Conference_Policies]] of all kinds!

== Shortly before the Conference ==

=== Keynotes ===
# Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc

=== Email Boilerplates / templates ===
* [[ConferenceOrientationEmail|Quick orientation email for newer folks]] - Send out at least a week in advance before conference...
* [[FreenodeIrcConnection|Freenode IRC connection]]
** Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.
** Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are "private" IP ranges used for connection sharing.)
** Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:
** I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)
** Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.

== At the Conference ==

===Keynotes===
# Speaker gifts
# Dinner plans

=== Timers ===
* Sit in the front of the room
* Have several people
* You may want to use an extra machine
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/

=== Lightning Talks ===
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

===PreConf===
# make sure projector avail for each session
# whiteboards or reasonable facsimile thereof
# everyone wants a power outlet

=== Conference ===
# power - everyone would like to plug in their laptop (and possibly their phone)
# IRC Monitor for podium during speaker changes?

===Photography===

* Consider different colored lanyards to articulate personal photography preferences.
** Portland/2015 had color-coded lanyards:
*** Green = it's ok to take my picture
*** Yellow = please ask before taking my picture
*** Red = don't take my picture

=== Podium ===
# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide an apple box for presenters who would like to use one.

=== Video ===
# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Live Blogging ===
Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.

=== Ask Anything===
* Add to volunteer page to have a moderator or do a general call out
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )

===Book Raffle===
See details here: https://wiki.code4lib.org/BookRaffle

* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table

=== Flipcharts ===
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/

=== Hospitality Suite ===
# having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening
# making sure the mess left for cleaning staff is an appropriate mess
# making sure the noise made near other hotel guests is an appropriate noise
# having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite

== Suggested Timeline ==
* See [[C4L2010planning]] for an example
* See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit Code4Lib 2014 planning schedule] planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.
* Ideal to have program set before registration, including pre-conf
** also allows clarity for how many spots are avail for non-presenters

===Calls for Hosting===
No one has claimed responsibility for putting out the call and setting the deadline. Consider having this task as the host committee, the voting committee, or perhaps the whatever committee.

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Some Suggested Readings ==
[https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

[[Category: Code4Lib2010]]
[[Category: Code4Lib2011]]
[[Category: Code4Lib2012]]
[[Category: Code4Lib2013]]
[[Category: Code4LibCon Planning]]

BookRaffle

2020-04-03T19:07:13Z

JulieSwierczek: added boilerplate message

BookRaffle

2020-04-03T19:03:46Z

JulieSwierczek: added list of companies that contributed in 2020

BookRaffle

2020-04-03T18:53:42Z

JulieSwierczek: added lessons learned from Sarah Swanz at code4lib 2020

=Lessons Learned=
If you have too much stuff to give away, let winners select more than one prize.

It's useful to break up the giveaways into groups of three. This takes about 5-7 minutes, and still leaves time for other announcements at the podium.

At least two people should handle the raffle so that one person can call the names and the other person can handle prize distribution. Also, someone needs to note the names of the winners so they can be removed from the next raffle.

Timing is critical. Giveaways immediately after lunch go faster because most attendees come back to the room for the next session. Slots after a poster session or between lightning talks and breakout sessions are much slower, as many people choose to take a break and not return to the room. It is therefore necessary to call lots of names before selecting someone present in the room. Giveaways on the final day are avoided since attendance is lower that day.

For fun, have a sound tech add a drum roll.

In 2020, several publishers gave an ebook license or discount code for all attendees. It might be better to request more of those kinds of rewards from publishers and do fewer individuals prizes.

= Book Raffle =

It would be nice to hit up some publishers for books to raffle off at the conference. If you've got ideas add them below under the name of the publisher. Most tech publishers have user group coordinators that are more than happy to make donations available.

==Addison-Wesley==
* [http://www.pearsonhighered.com/educator/product/Practice-of-System-and-Network-Administration-The/9780321492661.page Practice of System and Network Administration, 2E]

== APress ==

== Manning ==

* [http://manning.com/passin/ Explorer's Guide to the Semantic Web]

== Morgan & Claypool Publishers==
* [http://www.morganclaypool.com/doi/abs/10.2200/S00215ED1V01Y200907ICR009 Reading and Writing the Electronic Book]
* [http://www.morganclaypool.com/toc/wbe.1/1/1 Publishing Cultural Heritage on the Semantic Web] (maybe not out yet)
* [http://www.morganclaypool.com/doi/abs/10.2200/S00334ED1V01Y201102WBE001 Linked Data: Evolving the Web into a Global Data Space]
* [http://www.morganclaypool.com/doi/abs/10.2200/S00371ED1V01Y201107AIM013 Human Computation]
* [http://www.morganclaypool.com/doi/abs/10.2200/S00336ED1V01Y201102CSL003 Science Fiction Prototyping: Designing the Future with Science Fiction]
* Maybe other books from the [http://www.morganclaypool.com/toc/icr/1/1 Synthesis Lectures on Information Concepts, Retrieval, and Services]
* ...

== Morgan Kaufmann ==

* [http://www.elsevierdirect.com/product.jsp?isbn=9780123735560 Semantic Web for the Working Ontologist]

==No Starch Press==
* [http://nostarch.com/ejs| Eloquent Javascript]
* [http://nostarch.com/lyah.htm| Learn You a Haskell for Great Good!]

== O'Reilly ==
* ...

== Oxygen XML ==
* Licenses

== Packt Publishing ==
* ...

== Pragmatic Programmers ==

* [http://www.pragprog.com/titles/gsdgis/desktop-gis Desktop GIS: Mapping the Planet with Open Source Tools]
* [http://www.pragprog.com/titles/fr_ltp/learn-to-program Learn to Program]
* [http://www.pragprog.com/titles/pad/practices-of-an-agile-developer Practices of an Agile Developer]
* [http://www.pragprog.com/titles/ajax/pragmatic-ajax Pragmatic Ajax]
* [http://www.pragprog.com/titles/tsgit/pragmatic-version-control-using-git Pragmatic Version Control Using Git]
* [http://www.pragprog.com/titles/svn2/pragmatic-version-control-using-subversion Pragmatic Version Control Using Subversion]
* [http://www.pragprog.com/titles/jaerlang/programming-erlang Programming Erlang]
* [http://www.pragprog.com/titles/ruby/programming-ruby Programming Ruby]
* [http://www.pragprog.com/titles/vsscala/programming-scala Programming Scala]
* [http://www.pragprog.com/titles/tpp/the-pragmatic-programmer The Pragmatic Programmer]
* [http://www.pragprog.com/titles/pad/practices-of-an-agile-developer Practices of an Agile Developer]

[[Category:Code4Lib2009]]

2020 Book Giveaway Documents

2019-10-16T12:59:03Z

JulieSwierczek: added received items

[[User:JulieSwierczek|Julie Swierczek]] has a planning document in Google. If you join the committee, email Julie for access.

Once the committee work is finished, we'll integrate the document contents into the [[BookRaffle|Book Raffle]] page.

Items received from:
* ALA Neal-Schuman
* Routledge/Productivity Press (2 copies)

2020 Book Giveaway Documents

2019-10-05T13:14:55Z

JulieSwierczek: added info on working document

Code4Lib 2020 Conference Committees

2019-05-17T14:22:37Z

JulieSwierczek: volunteered to Chair

= Code4Lib 2020 Conference Committees =

Hosting a conference is incredibly 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 2020 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: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA
* Dates: March 08 (pre-con) - 22, 2020
** Pre-conferences: March 08, 2020
** Main meeting: March 09-11, 2020
** Post conference activities: Coming Soon

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

* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2020 Website Working Group Documents|2020 Website Working Group Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* Your Name Here - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* Your Name Here- Volunteer

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

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* 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.

[[2020 Keynote Documents|2020 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2020 Pre-conference Documents|2020 Pre-conference Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* 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.

[[2020 Program Documents|2020 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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.

[[2020 Scholarship Documents|2020 Scholarship Documents]]

* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2020 T-Shirt Documents|2020 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]

* Your Name Here Contact aka Co-Chair
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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, of course, actually running the camera during the conference.

[[2020 Streaming Video Documents|2020 Streaming Video Documents]]

* Your Name Here - Chair
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

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

[[2021 Host Voting Documents|2021 Host Voting Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Roy Tennant - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:lillyho@gmail.com Lilly HS HO] - 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).

[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]

* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

[[2020 Accessibility Documents|2020 Accessibility Documents]]

* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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.

[[2020 Whatever Documents|2020 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2020]]

User:JulieSwierczek

2019-05-17T14:20:23Z

JulieSwierczek: changed title and email

Julie C. Swierczek, Associate Librarian for Collection Description and Imaging, Folger Shakespeare Library, jswierczek {at...} folger {dot} edu

Main Page

2018-03-10T15:12:23Z

JulieSwierczek: Added link to new Teaching beginners page

{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"
| style="width:54%; color:#000;" |

{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4lib wiki</div>
|}


__NOTOC__
| style="width:20%; font-size:95%;vertical-align:top; " |
* [[#About Code4Lib|About Code4Lib]]
* [[#Software Usage and Documentation|Software Usage and Documentation]]
* [[#Current topics|Current topics]]
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]
| style="width:13%; font-size:95%;" |
* [[#Code4Lib 2018 Conference|2018 Conference]]
* [[#Local / Regional Groups|Local / Regional Groups]]
* [[#Interest Groups|Interest Groups]]
* [[#Earlier Conferences and events|Earlier Conferences and events]]
|}


{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"

| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"
|-

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies
* [[How to hack code4lib]] - For those newer to the community
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)
**"How do we make code4lib a more inclusive place for newcomers? Or, how do we quickly indoctrinate newbies to our values and ways of doing things?"
**Suggestions, ideas, and follow-up actions solicited.
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders
* [[Mentorship Program]]
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.
* [[Zoia or the Code4Lib IRC bot]]
|-

== 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
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist
|-

== Current topics ==

* [[Code4Lib Regional Meeting Streaming]]
* [[Code4Lib Website Update]]
* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]
* [[Parsing Library Data]]
* [[Robots Are Our Friends]]
* [[Libraries Sharing Code]]
* [[Code4Lib Tagline brainstorm]]
* [[Fiscal Continuity]]
** [[Fiscal Sponsorship Working Group]]
* [[Accessibility]]
* [[Teaching beginners]]
|-

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]
* [http://journal.code4lib.org journal.code4lib.org]
|-

== Code4Lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

|}
| style="border:1px solid transparent;" |
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|

{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"

==Code4Lib 2018 Conference==
{{:Category:Code4Lib2018}}
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]
* [[2018_Conference_Volunteers|2018 Conference Volunteers]]
* [[2018_Social_Activities|2018 Social Activities]]
* [[Code4Lib2018_Posters|2018 Poster Presentations]]
* [[Code4Lib2018_Breakout_Sessions|2018 Breakout Sessions]]
* [[Code4Lib2018_Lightning_Talks|2018 Lightning Talks]]
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"

==Code4Lib 2017 Conference==
{{:Category:Code4Lib2017}}
* [[2017_Code4Lib_T-Shirt_Design_Competition|2017 Code4Lib T-Shirt Logo Design Competition]]
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]
|-

== Local / Regional Groups ==

=== United States ===
* [[NEC4L|New England Code4lib]] - New England
* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest
* [[South_Central|Code4Lib South Central]] - Texas, Oklahoma, Louisiana, Arkansas, New Mexico
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[Western|Code4Lib West]] - California North and South

=== Canada ===

* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces
* [[North|code4lib North]] - Ontario and surrounding areas
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''

=== Europe ===
* [[NL|Code4Bib]] - Dutch Code4Bib
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers

=== Asia/Pacific ===
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.

=== Middle East ===
* [[Qatar|Code4Lib Qatar]] - Doha ''(new in 2018)''
|-

== 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
* [[Fiscal_Continuity|Fiscal Continuity]] - A group that explored from 2016 to 2017 whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)
* [[Fiscal_Sponsorship_Working_Group|Fiscal Sponsorship Working Group]] - A group formed to implement a fiscal sponsorship agreement per the results of the [[Fiscal_Continuity#Fiscal_Options_Vote|fiscal options vote]] in late 2017
|-

|}
|}

== Earlier Conferences and events ==
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IN
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR
[[Conference Financial History At A Glance]]

=== Older Conference T-Shirt Designs ===
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]

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

Teaching beginners

2018-03-10T15:10:40Z

JulieSwierczek: Created page and added content from notes from code4lib 2018 breakout sessions and talk.

= Teaching Beginners =

People working in our fields often find themselves teaching technology to beginners. This may be through formal workshops offered to the public or to peers in our fields; to colleagues who need to learn new technology in the workplace; or through informal peer teaching where we share technology with others in any setting. Below are some tips and ideas from the code4lib community on teaching technology to beginners. (Some of these tips came from [http://2018.code4lib.org/talks/for-beginners-no-experience-necessary a talk] and two breakout sessions at [http://2018.code4lib.org/ code4lib 2018].)

== General tips ==
*Do not assume experience with Git or the Command Line. Be careful about the Bash shell as well. If you want your attendees to have familiarity with certain tools, don’t assume that they do. It is especially annoying if you go to a workshop where those tools are not the focus, but it is assumed that attendees are well-versed in them.

*At the same time, when teaching it can be good to send people to do an exercise and, if they can't figure it out or run into issues, they can use git to move further along in the program so they are caught up with the rest of the class. However, if git is not the focus of the workshop and it is not an assumed skill, the git commands to do so should be very clearly communicated to the attendees.

*When you distribute code that is long, number sections in the comments so people can more easily navigate it. Number the exercises. Numbers give us a common language for navigating.

*Heavily comment code with pseudo-code and explanations about what each section does.

*Notebooks for teaching programming, such as the [https://jupyter.org/ Jupyter notebook] can give users a great intro, because you can give them the code to run through the notebook.

*Instead of saying that a particular idea is ‘easy’ or ‘hard’, say that the idea is ‘foundational’ or a ‘building block’, and this other idea is ‘more complex’. If an attendee is struggling with an idea, saying that it is ‘easy’ only makes the person feel worse. They already felt stupid because they didn’t get the idea; now they feel even more stupid because they didn’t get an ‘easy’ idea.

*If you encounter students who are either silent or are being angry towards you, it may be that they are trying not to cry either by being stonily silent or covering it with another emotion (i.e., anger.) This is not a funeral, it's a workshop, so people don't want to cry.

*As an instructor, avoid saying too much, such as, "We'll do x here, but if you are doing y you would do a and if you were doing z you would do b". If you are teaching x, just say, "We will do x here." Full stop. Don't show off by bringing up other examples. Some people talk a lot when they are nervous, and teaching and public speaking can make people nervous. Also, most people will talk to fill silence in a conversation. Be okay with not talking and having quiet so people can think and process information.

*Similarly, plan silences and pauses. It is hard to learn something complex when someone is talking and you are trying to figure out if you need to be listening while also trying to do this new task.

*Don’t make fun of people who mispronounce words, they learned them from reading. Similarly, if someone has clunky code it may because they are self-taught; be gentle when you show them a new way. (See the [https://www.recurse.com/code-of-conduct Recurse Center Rules] on 'well, actually' and other social problems.)

*Reading good code on github is good workshop takeaway. It is great for workshop leaders to hand out lists of projects people can investigate on their own. It is also important to demonstrate projects with good documentation.

*If attendees are allowed to choose their own operating systems for a workshop, then the instructor needs to provide instructions for Mac, Linux, and Windows, if they are different. Instructors should not just wave their hands and say 'I'll show you this system. The other ones are different." Even better is to use a platform-agnostic approach so that beginners can focus on the specific tool and not spend time trying to figure out problems with their computers. Also, when beginners make mistakes, they can just start over and not have ruined the whole thing.

*There are Chrome extensions that run a web server in the browser. There are web-based interpreters for programming. It may be nice to give people the option to use a web-based interpreter or a desktop one, so those who feel more comfortable with a desktop one can do so, but everyone can play in the web-based one.

*When designing a workshop, try to work with a fresh install and without admin privileges. You may not realize that you need dependencies or admin privileges until you test.

*Avoid sports metaphors or idioms that may not make sense outside a certain cultural group. If attendees need to have knowledge of a particular domain prior to taking the workshop, that should be clear in the workshop description.

*Asking attendees to raise their hands if they need help is problematic. It is ableist. It also requires people to self-identify as needing help in front of a room of their peers. One alternative approach is to provide attendees with two different color post-it notes. As the workshop progresses, they attach one color to the top of their computer when they have finished an exercise. They use another color to indicate when they need assistance. This still requires self-identification of needing help to an extent, but it is not as obvious as raising a hand.

== Gaining teaching experience ==
*If you want some teaching experience, collaborate with instructors to help them run workshops. When someone offers a workshop, don’t be afraid to email and ask if they want teaching assistants, or a co-teacher. They may be happy to have help. At the same time, if teachers do not want help, they should not feel pressured to accept such requests.

== Learning how to teach beginners ==
*Library organizations seem to be good at providing professional development opportunities for training librarians for reference instruction, but not for technology instruction. We need professional development opportunities for teaching technology to adults.

*We don’t need to reinvent the wheel; we just need to talk to the people who work in this area already. For example, instructor training is offered by [https://software-carpentry.org/ Software Carpentry] and [https://librarycarpentry.github.io/ Library Carpentry].

*Another resources is the [https://www.diglib.org/groups/digital-library-pedagogy/ DLF Digital Library Pedagogy Group].

*We need training on peer teaching and mentoring. This is especially important in senior/junior technology job relationships. This is often part of someone’s job description, but we are not formally trained how to do this. Pair programming can be good if people are not too far apart in skill, so they both learn from each other; if they are too far part, it can be frustrating for each participant. Pair programming is not for everyone, though.

== Helping attendees determine if they should attend your workshop ==
*A key problem is that workshops are sometimes advertised as being ‘for beginners, with no experience necessary’. But this is misleading, as the instructors and potential attendees will likely have very different ideas about what that means. A better approach is for instructors to list key skills and experiences, or analogous skills and experiences, that attendees should have before taking the workshop. As an example, people who have used formulas in Excel - even sporadically - are on a completely different level from beginners who are not sure how to use the mouse.

*Instructors should help attendees answer the question, “Is this workshop for me?”

*Recommend people try exercises at [https://www.codecademy.com/ codecademy] or other free online training sites to see if they want to learn more. It may help them decide that now is not the time for them to pursue training in this area. (It's okay for someone to decide that this is not a good time to learn something.) Caring for kids or aging parents; fighting poverty and working multiple jobs; and other personal obligations can interfere with people's ability to find time and mental energy for learning. Sometimes they really want you to give a very gentle introduction with a lot of hand-holding. This is okay. Also, their frustration tolerance level may be very low because of external factors. This is okay, too.

*The people involved with [https://software-carpentry.org/ Software Carpentry] have learned that if you call a workshop ‘intermediate’, no one signs up. So maybe we need to drop this beginner/intermediate/advanced labeling altogether. Just talk about your prerequisites and expected outcomes.

== Respecting the time required for excellent teaching ==
*If teaching colleagues is part of your job, it should be in your job description, such as “10% of time devoted to developing teaching materials and teaching peers”.

*People should be paid to design and teach workshops. Workshop design and delivery requires skill and energy, and people should not be doing this for free. At the same time, be careful of the cost of workshops. Not everyone gets institutional support and they have to make a lot of sacrifices to come to your workshop. Most people in this field are not independently wealthy.

== Creating a positive learning environment ==
*There should be a Code of Conduct for attendees. If nothing else, have attendees read the [https://www.recurse.com/code-of-conduct Recurse Center Rules] (also known as the Hacker School Rules). This helps curtail situations where attendees disparage each other’s operating systems; engage in mansplaining; or respond to a basic question with an overly complex response requiring esoteric techniques that is deliberately designed to confuse and belittle the questioner.

== Texts for teaching and learning ==
*Elizabeth Wickes gave a lightning talk at code4lib 2018 where she asked about programming textbooks for teaching LIS students that do not require trigonometry or advanced skills in specific knowledge domains. Texts that might be used as a model are No Starch Press books like “Learning from Scratch” and “Python for Kids”. Since they are written for children, they do not assume college- or even high school- level familiarity with particular knowledge domains. They are models of clarity.

*The book [http://www.openbookproject.net/thinkcs/python/english2e/ “How to Think Like a Computer Scientist”] uses Python, but focuses more broadly on thinking programmatically.

== Visual programming languages ==
*If you want to teach adults with a visual programming language like Scratch or Blockly, but you do not want to say to your students, “we’re going to do programming for kids”, Blockly is slightly more adult-oriented than Scratch. At the same time, Scratch is not a bad idea. In fact, it may be a relief to your students if you tell them that they are going to do a gentle introduction to programming through one of these languages.

== Next steps ==
*For self-taught and self-directed learners, some recommended resources are [https://www.codecademy.com/ codecademy], [https://www.udemy.com/python-video-workbook/landing-page/ Udemy’s Python workbook course], and the [https://www.coursera.org/specializations/python University of Michigan’s “Python for Everybody” specialization on Coursera]. [https://coderdojo.com/ Coderdojo] and other code practicing sites let you look at other people’s solutions, so you can learn by seeing what other people do

== Teaching workshop series or multi-week courses ==

*Respect students’ cognitive load. There are limits to how much a person can learn at any one moment. If students are feeling overloaded, that may be a good signal to do additional exercises for practice at their current level of understanding, instead of moving forward to a new topic.

*Engage students in dialogue to find out about their mental models. For beginners, what computers do is largely a black box, and they have to come up with models to explain what is happening in the black box until they gain sufficient knowledge to understand what is actually happening in the black box. Their models might be problematic at the early stages of learning; they may make connections where there are none, or assume causality where none exists. Talking them through their models can help us find and correct these misperceptions.

2018 Conference Volunteers

2018-02-01T15:41:01Z

JulieSwierczek: /* The Whatever Crew */

= Code4Lib 2018 Conference Volunteers =

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

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

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

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

Monday 2/12:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Tuesday 2/13:
* Time TBD:''Your Name Here''

Wednesday 2/14:
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:durden@umd.edu David Durden]

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

Preconference Setup and sessions Tuesday 2/13:
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Tuesday 2/13:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:michael@dp.la Michael Della Bitta]
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Thursday 2/15:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Friday 2/16:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

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

* Before the conference: [[User:Anarchivist|Mark Matienzo]]
* Time TBD: ''Your Name Here''

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

* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

==MCs==

Wednesday 2/14:
* Time TBD (AM?): Becky Yoose
* Time TBD: (PM, not during my AM talk): [mailto:jswierc1@swarthmore.edu Julie Swierczek]

Thursday 2/15:
* Time TBD (AM, but not if that's when my talk is): Dre
* Time TBD: Christina Harlow

Friday 2/16:
* AM Session: Mary Jinglewski

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

Wednesday 2/14:
* Time TBD: Primary: ''[mailto:liblna@emory.edu Laura Akerman]'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]

Thursday 2/15:
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''

Friday 2/16:
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''

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

* [mailto:bomanca@miamioh.edu Craig Boman]
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580
* [mailto:jswierc1@swarthmore.edu Julie Swierczek]
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

[[Category: Code4Lib2018]]

2018 Conference Volunteers

2018-02-01T15:40:41Z

JulieSwierczek: /* The Whatever Crew */

= Code4Lib 2018 Conference Volunteers =

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

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

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

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

Monday 2/12:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Tuesday 2/13:
* Time TBD:''Your Name Here''

Wednesday 2/14:
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:durden@umd.edu David Durden]

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

Preconference Setup and sessions Tuesday 2/13:
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Tuesday 2/13:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:michael@dp.la Michael Della Bitta]
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Thursday 2/15:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Friday 2/16:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

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

* Before the conference: [[User:Anarchivist|Mark Matienzo]]
* Time TBD: ''Your Name Here''

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

* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

==MCs==

Wednesday 2/14:
* Time TBD (AM?): Becky Yoose
* Time TBD: (PM, not during my AM talk): [mailto:jswierc1@swarthmore.edu Julie Swierczek]

Thursday 2/15:
* Time TBD (AM, but not if that's when my talk is): Dre
* Time TBD: Christina Harlow

Friday 2/16:
* AM Session: Mary Jinglewski

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

Wednesday 2/14:
* Time TBD: Primary: ''[mailto:liblna@emory.edu Laura Akerman]'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]

Thursday 2/15:
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''

Friday 2/16:
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''

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

* [mailto:bomanca@miamioh.edu Craig Boman]
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580
* [mailto: jswierc1@swarthmore.edu Julie Swierczek]
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

[[Category: Code4Lib2018]]

2018 Conference Volunteers

2018-02-01T15:39:24Z

JulieSwierczek: /* MCs */

= Code4Lib 2018 Conference Volunteers =

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

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

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

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

Monday 2/12:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Tuesday 2/13:
* Time TBD:''Your Name Here''

Wednesday 2/14:
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:durden@umd.edu David Durden]

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

Preconference Setup and sessions Tuesday 2/13:
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Tuesday 2/13:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:michael@dp.la Michael Della Bitta]
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Thursday 2/15:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Friday 2/16:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

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

* Before the conference: [[User:Anarchivist|Mark Matienzo]]
* Time TBD: ''Your Name Here''

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

* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

==MCs==

Wednesday 2/14:
* Time TBD (AM?): Becky Yoose
* Time TBD: (PM, not during my AM talk): [mailto:jswierc1@swarthmore.edu Julie Swierczek]

Thursday 2/15:
* Time TBD (AM, but not if that's when my talk is): Dre
* Time TBD: Christina Harlow

Friday 2/16:
* AM Session: Mary Jinglewski

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

Wednesday 2/14:
* Time TBD: Primary: ''[mailto:liblna@emory.edu Laura Akerman]'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]

Thursday 2/15:
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''

Friday 2/16:
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''

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

* [mailto:bomanca@miamioh.edu Craig Boman]
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

[[Category: Code4Lib2018]]

2018 Conference Volunteers

2018-02-01T14:56:30Z

JulieSwierczek: volunteered to MC

= Code4Lib 2018 Conference Volunteers =

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

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

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

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

Monday 2/12:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Tuesday 2/13:
* Time TBD:''Your Name Here''

Wednesday 2/14:
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:durden@umd.edu David Durden]

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

Preconference Setup and sessions Tuesday 2/13:
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Tuesday 2/13:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD:''Your Name Here''
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Thursday 2/15:
* Time TBD: [[User:Khaley|Kathleen Haley]]
* Time TBD: ''Your Name Here''

Friday 2/16:
* Time TBD: [mailto:michael@dp.la Michael Della Bitta]
* Time TBD: ''Your Name Here''

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

Wednesday 2/14:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Thursday 2/15:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

Friday 2/16:
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);

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

* Before the conference: [[User:Anarchivist|Mark Matienzo]]
* Time TBD: ''Your Name Here''

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

* Time TBD: ''Your Name Here''
* Time TBD: ''Your Name Here''

==MCs==

Wednesday 2/14:
* Time TBD (AM?): Becky Yoose
* Time TBD: (PM, not during my AM talk): [https://wiki.code4lib.org/User:JulieSwierczek Julie Swierczek]

Thursday 2/15:
* Time TBD (AM, but not if that's when my talk is): Dre
* Time TBD: Christina Harlow

Friday 2/16:
* AM Session: Mary Jinglewski

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

Wednesday 2/14:
* Time TBD: Primary: ''[mailto:liblna@emory.edu Laura Akerman]'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]

Thursday 2/15:
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''

Friday 2/16:
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''

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

* [mailto:bomanca@miamioh.edu Craig Boman]
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

[[Category: Code4Lib2018]]

User:JulieSwierczek

2018-02-01T14:54:17Z

JulieSwierczek: updated contact info

Julie Swierczek, Friends Historical Library and Swarthmore College Peace Collection, jswierc1 {...at..} swarthmore dot edu

2017 Conference Volunteers

2017-02-13T13:53:26Z

JulieSwierczek: Added my name as a livestream QA (remote) volunteer on 3/7

= Code4Lib 2017 Conference Volunteers =

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

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

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

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

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

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

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

Monday 3/6:
* 8a-9am: 6 UCLA
* 12:30p-1:30p: 6 UCLA

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Wednesday PM
* Primary: ''Your Name Here''
* Backup: ''Your Name Here''

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

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

* Lawrence Olliffe
* [mailto:bobbi_fox@harvard.edu Bobbi Fox]
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

[[Category: Code4Lib2017]]

NECode4lib 2015 Fall

2015-11-30T16:23:45Z

JulieSwierczek: removed my contributions since I will not be able to attend

Please join us Friday, December 4, in Hanover, NH for the Fall 2015 NECode4Lib conference. This informal conference will feature sessions covering technology in libraries, archives and museums in the New England area.

===Location===
This NECode4Lib meeting will be hosted by the Dartmouth College Library.

'''When''' - Friday, December 4th

'''Where''' - Jones Media Center, [http://m.dartmouth.edu/map/campus?feed=f8a86d47cf&group=dartmouth&featureindex=65&category=f8a86d47cf%3A5&_b=%5B{%22t%22%3A%22Map%22%2C%22lt%22%3A%22Map%22%2C%22p%22%3A%22index%22%2C%22a%22%3A%22%22}%5D Baker-Berry Library], Dartmouth College

'''Registration Cost''' - Free!

'''Registration Link''' - https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

'''Planning Committee''' - Joe Montibello (joseph.montibello@dartmouth.edu), Jenny Mullins (jennifer.l.mullins@dartmouth.edu), Carla Galarza (carla.m.galarza@dartmouth.edu), Laura Braunstein (laura.r.braunstein@dartmouth.edu), Shaun Akhtar (shaun.y.akhtar@dartmouth.edu)

===Logistics===
====Transportation====
* Hanover is a few minutes' drive from Exit 18 on I-89 or Exit 13 on I-91.
* The private [http://dartmouthcoach.com/ Dartmouth Coach] provides bus service to Hanover from South Station and Logan Airport in Boston and from Midtown Manhattan in New York City.
* On-campus parking will be free but attendees will need to register for a parking permit ahead of time - there will be a separate Eventbrite "ticket" available that will allow you to register for free parking.
* If you are interested in carpooling, please fill out this [https://docs.google.com/spreadsheets/d/1UDCQiitqEwGjmLZnsjys4BxgRDgODgHO2elks1d7Jmk/edit?usp=sharing rideshare sign-up] and use the contact information there to connect with other attendees.

====Hotels====
Hotel blocks are being held for the nights of Thursday, December 3 and Friday, December 4 under Code4Lib -- mention this event when calling to make your reservation. Hotel blocks will be held at these rates until November 3. For additional suggestions, or if you need to book housing after the blocks have expired (or if they have sold out), please email the organizers at Code4Lib@dartmouth.edu

{| class="wikitable"
|-
! Hotel !! Rate !! Phone
|-
| [http://www.hanoverinn.com/ Hanover Inn] (five minute walk from Baker-Berry Library) || $129 || 603-643-4300
|-
| [http://www.sixsouth.com/ Six South Street Hotel] (ten minute walk) || $114 || 603-643-0600
|-
| [http://www.elementhanoverlebanon.com/ Element Hotel] (ten minute drive) || $129 || 603-448-5000
|-
| [http://www.marriott.com/hotels/travel/lebcy-courtyard-hanover-lebanon/ Courtyard by Marriott] (ten minute drive) || $145 || 603-643-5600
|}

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct If an incident occurs, please use the following contact information:

Conference organizers: 
Joe Montibello (cell) - 603-553-0393 
Jenny Mullins (cell) - 412-7128-1882 
Dartmouth Safety & Security: 603-646-4000 
Hanover Police Department: 603-643-2222 
Grafton County Support Center Against Domestic Violence and Sexual Assault: 603-448-5922 

==Programming==
===Programming Sign-up===
Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a wiki account, you can contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Joe Montibello (joe@dartmouth.edu) to have your presentation/lightning talk/discussion topic added below for you.

====Presentations====
15-20 minutes talks.

# [[User:Otterfan|Ben Florin]] - Recommending librarians using Elasticsearch and LC Call Numbers
# [[User:Roconnell|Rob O'Connell]] - Browsing your collection using x and restful servers
# [[User:AlicePrael|Alice Prael]] and Jeff Erickson - Where to Start Implementing Digital Preservation
# [[User:sanderson|Steven Anderson]] and [[User:Eenglish|Eben English]] (Boston Public Library) - RDF and Linked Data
#
#
#
#

====Lightning Talks====
A lightning talk is a fast-paced, 5-minute talk on the topic of your choice.

# [[User:RoseReynolds|Rose Reynolds]] -A Tour of the Library: Moving from analog to digital
# [[User:JennyMullins|Jenny Mullins]] - Script for Success: A micro-service approach to quality control for digital preservation
# [[User:AlicePrael|Alice Prael]] - Intro to Born Digital Processing Tools and Workflows
#
#
#
#
#
#
#

====Discussion Topics====
List some topics you are interested in talking to others during breakout time.

#
#
#

===Topics of interest===
Prospective attendees shared these responses to the survey question "What topics would you like to see presented on?"

* Digital preservation workflows.
* Tools for improving information management capabilities
* Blacklight
* Digital preservation tools
* Data visualization
* Cyber security in libraries
* Any Alma shops using import profiles? How are people managing their e-resources on a large scale? What cool ways are people enriching their records with non-library metadata - how are they doing this technically and what cultural changes are necessary to gain approval - is this a project with a specific scope or part of ongoing enrichment?
* Discovery tool improvements, innovative ways to spotlight collections online
* DPLA MAP as local data model
* Bibframe and Drupal
* I'd like to explore a career as a systems librarian, and I would love it if someone did a presentation on "what I wish I had known before I became a systems librarian" or "what you need to know to be a systems librarian" or "a day in the life..." or some similar overview. I recognize that 'systems librarian' can mean a bazillion different things, but I'm sure a pro could get to the core of it. Also, this would be very newbie-oriented, so maybe it's not appropriate for this meeting. Still, it's just an idea.
* Open source coding and programming basics, archival description (EAD) tools and applications...
* Linked data, data visualization, repositories, discovery environments
* Linux, HTML5, Python, Javascript
* Blacklight, Solr, Library location service
* Video game design in libraries, particularly with teens; parallels between storytelling and video game design experiences.
* TEI, text/data mining
* Analytics, repository development, metadata enrichment, server administration, user interface testing results, complex RDF descriptive metadata modeling, etc.
* Publication workflows in libraries
* Digital humanities and archives, linked data, diversifying the profession(s), digital preservation and born digital materials
* Sustainability planning, digital scholarship for subject liaisons, project development, hands-on coding/tool sessions
* Linked open data
* Digital curation, digital preservation, digital scholarship, born-digital preservation, digital collections.
* Database and collections management-related such as open source technologies that can assist in these areas.
* Coding for preschoolers/early elementary students, coding in school libraries
* The potential of tech in libraries and beyond.
* Web design; user testing; learning resources for junior-level web developers
* Open source programs for collaborative writing, editing, and publishing. How to build on open source programs in your special area of interest. Programs and tools for data visualization. Programs and tools for digital exhibits. Programs for managing metrics. How to talk to programmers and software designers- how to explain your vision so the result is what was expected. What programs are most important for library staff to know about? Ruby on Rails, Python.....? The anatomy of a program.
* Advantages of non-digital approaches.
* Digital preservation approaches (such as variable media and crowdsourcing) and techniques (such as emulation), as well as strategies for teaching digital curation.
* Asynchronous storage strategies. Advanced search tools for repositories on the web. Indexing metadata with tools/products other than Solr. All the topics.
* Code for websites. RDF ontology for library and archives.

==Schedule==

===Friday, December 4===

Registration and coffee starts at 9 a.m. Program starts at 10 and continues through late afternoon/early evening. Further details TBA.

==Registration==
https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

==Mailing list==
NECode4Lib has a low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

NECode4lib 2015 Fall

2015-10-16T13:14:55Z

JulieSwierczek: added link to user page

Please join us Friday, December 4, in Hanover, NH for the Fall 2015 NECode4Lib conference. This informal conference will feature sessions covering technology in libraries, archives and museums in the New England area.

===Location===
This NECode4Lib meeting will be hosted by the Dartmouth College Library.

'''When''' - Friday, December 4th

'''Where''' - Jones Media Center, [http://m.dartmouth.edu/map/campus?feed=f8a86d47cf&group=dartmouth&featureindex=65&category=f8a86d47cf%3A5&_b=%5B{%22t%22%3A%22Map%22%2C%22lt%22%3A%22Map%22%2C%22p%22%3A%22index%22%2C%22a%22%3A%22%22}%5D Baker-Berry Library], Dartmouth College

'''Registration Cost''' - Free!

'''Registration Link''' - https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

'''Planning Committee''' - Joe Montibello (joseph.montibello@dartmouth.edu), Jenny Mullins (jennifer.l.mullins@dartmouth.edu), Carla Galarza (carla.m.galarza@dartmouth.edu), Laura Braunstein (laura.r.braunstein@dartmouth.edu), Shaun Akhtar (shaun.y.akhtar@dartmouth.edu)

===Logistics===
====Transportation====
* Hanover is a few minutes' drive from Exit 18 on I-89 or Exit 13 on I-91.
* The private [http://dartmouthcoach.com/ Dartmouth Coach] provides bus service to Hanover from South Station and Logan Airport in Boston and from Midtown Manhattan in New York City.
* On-campus parking is available for $10/car. Please contact Shaun Akhtar (shaun.y.akhtar@dartmouth.edu) to make arrangements.
* We are also looking into helping arrange carpooling. More information will be distributed to registrants as we get closer to the event. Please contact Shaun at the address above with any questions.

====Hotels====
Hotel blocks are being held for the nights of Thursday, December 3 and Friday, December 4 under Code4Lib -- mention this event when calling to make your reservation. Hotel blocks will be held at these rates until November 3. For additional suggestions, or if you need to book housing after the blocks have expired (or if they have sold out), please email the organizers at Code4Lib@dartmouth.edu

{| class="wikitable"
|-
! Hotel !! Rate !! Phone
|-
| [http://www.hanoverinn.com/ Hanover Inn] (five minute walk from Baker-Berry Library) || $129 || 603-643-4300
|-
| [http://www.sixsouth.com/ Six South Street Hotel] (ten minute walk) || $114 || 603-643-0600
|-
| [http://www.elementhanoverlebanon.com/ Element Hotel] (ten minute drive) || $129 || 603-448-5000
|-
| [http://www.marriott.com/hotels/travel/lebcy-courtyard-hanover-lebanon/ Courtyard by Marriott] (ten minute drive) || $145 || 603-643-5600
|}

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct If an incident occurs, please use the following contact information:

Conference organizers: 
Joe Montibello (cell) - 603-553-0393 
Dartmouth Safety & Security: 603-646-4000 
Hanover Police Department: 603-643-2222 
Grafton County Support Center Against Domestic Violence and Sexual Assault: 603-448-5922 

==Programming==
===Programming Sign-up===
Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a wiki account, you can contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Joe Montibello (joe@dartmouth.edu) to have your presentation/lightning talk/discussion topic added below for you.

====Presentations====
15-20 minutes talks.

# [[User:JulieSwierczek|Julie Swierczek]] - Digital Preservation for Everyone: A 15-Minute Romp through the OAIS Model
#
#

====Lightning Talks====
A lightning talk is a fast-paced, 5-minute talk on the topic of your choice.

#
#
#

====Discussion Topics====
List some topics you are interested in talking to others during breakout time.

# Digital Preservation: Tools, Workflows, Policies, the Good, the Bad, the Ugly, etc. ([[User:JulieSwierczek|Julie Swierczek]])
#
#

===Topics of interest===
Prospective attendees shared these responses to the survey question "What topics would you like to see presented on?"

* Digital preservation workflows.
* Tools for improving information management capabilities
* Blacklight
* Digital preservation tools
* Data visualization
* Cyber security in libraries
* Any Alma shops using import profiles? How are people managing their e-resources on a large scale? What cool ways are people enriching their records with non-library metadata - how are they doing this technically and what cultural changes are necessary to gain approval - is this a project with a specific scope or part of ongoing enrichment?
* Discovery tool improvements, innovative ways to spotlight collections online
* DPLA MAP as local data model
* Bibframe and Drupal
* I'd like to explore a career as a systems librarian, and I would love it if someone did a presentation on "what I wish I had known before I became a systems librarian" or "what you need to know to be a systems librarian" or "a day in the life..." or some similar overview. I recognize that 'systems librarian' can mean a bazillion different things, but I'm sure a pro could get to the core of it. Also, this would be very newbie-oriented, so maybe it's not appropriate for this meeting. Still, it's just an idea.
* Open source coding and programming basics, archival description (EAD) tools and applications...
* Linked data, data visualization, repositories, discovery environments
* Linux, HTML5, Python, Javascript
* Blacklight, Solr, Library location service
* Video game design in libraries, particularly with teens; parallels between storytelling and video game design experiences.
* TEI, text/data mining
* Analytics, repository development, metadata enrichment, server administration, user interface testing results, complex RDF descriptive metadata modeling, etc.
* Publication workflows in libraries
* Digital humanities and archives, linked data, diversifying the profession(s), digital preservation and born digital materials
* Sustainability planning, digital scholarship for subject liaisons, project development, hands-on coding/tool sessions
* Linked open data
* Digital curation, digital preservation, digital scholarship, born-digital preservation, digital collections.
* Database and collections management-related such as open source technologies that can assist in these areas.
* Coding for preschoolers/early elementary students, coding in school libraries
* The potential of tech in libraries and beyond.
* Web design; user testing; learning resources for junior-level web developers
* Open source programs for collaborative writing, editing, and publishing. How to build on open source programs in your special area of interest. Programs and tools for data visualization. Programs and tools for digital exhibits. Programs for managing metrics. How to talk to programmers and software designers- how to explain your vision so the result is what was expected. What programs are most important for library staff to know about? Ruby on Rails, Python.....? The anatomy of a program.
* Advantages of non-digital approaches.
* Digital preservation approaches (such as variable media and crowdsourcing) and techniques (such as emulation), as well as strategies for teaching digital curation.
* Asynchronous storage strategies. Advanced search tools for repositories on the web. Indexing metadata with tools/products other than Solr. All the topics.
* Code for websites. RDF ontology for library and archives.

==Schedule==

===Friday, December 4===

Registration and coffee starts at 9 a.m. Program starts at 10 and continues through late afternoon/early evening. Further details TBA.

==Registration==
https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

==Mailing list==
NECode4Lib has a low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

NECode4lib 2015 Fall

2015-10-16T13:13:56Z

JulieSwierczek: added link to user page

Please join us Friday, December 4, in Hanover, NH for the Fall 2015 NECode4Lib conference. This informal conference will feature sessions covering technology in libraries, archives and museums in the New England area.

===Location===
This NECode4Lib meeting will be hosted by the Dartmouth College Library.

'''When''' - Friday, December 4th

'''Where''' - Jones Media Center, [http://m.dartmouth.edu/map/campus?feed=f8a86d47cf&group=dartmouth&featureindex=65&category=f8a86d47cf%3A5&_b=%5B{%22t%22%3A%22Map%22%2C%22lt%22%3A%22Map%22%2C%22p%22%3A%22index%22%2C%22a%22%3A%22%22}%5D Baker-Berry Library], Dartmouth College

'''Registration Cost''' - Free!

'''Registration Link''' - https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

'''Planning Committee''' - Joe Montibello (joseph.montibello@dartmouth.edu), Jenny Mullins (jennifer.l.mullins@dartmouth.edu), Carla Galarza (carla.m.galarza@dartmouth.edu), Laura Braunstein (laura.r.braunstein@dartmouth.edu), Shaun Akhtar (shaun.y.akhtar@dartmouth.edu)

===Logistics===
====Transportation====
* Hanover is a few minutes' drive from Exit 18 on I-89 or Exit 13 on I-91.
* The private [http://dartmouthcoach.com/ Dartmouth Coach] provides bus service to Hanover from South Station and Logan Airport in Boston and from Midtown Manhattan in New York City.
* On-campus parking is available for $10/car. Please contact Shaun Akhtar (shaun.y.akhtar@dartmouth.edu) to make arrangements.
* We are also looking into helping arrange carpooling. More information will be distributed to registrants as we get closer to the event. Please contact Shaun at the address above with any questions.

====Hotels====
Hotel blocks are being held for the nights of Thursday, December 3 and Friday, December 4 under Code4Lib -- mention this event when calling to make your reservation. Hotel blocks will be held at these rates until November 3. For additional suggestions, or if you need to book housing after the blocks have expired (or if they have sold out), please email the organizers at Code4Lib@dartmouth.edu

{| class="wikitable"
|-
! Hotel !! Rate !! Phone
|-
| [http://www.hanoverinn.com/ Hanover Inn] (five minute walk from Baker-Berry Library) || $129 || 603-643-4300
|-
| [http://www.sixsouth.com/ Six South Street Hotel] (ten minute walk) || $114 || 603-643-0600
|-
| [http://www.elementhanoverlebanon.com/ Element Hotel] (ten minute drive) || $129 || 603-448-5000
|-
| [http://www.marriott.com/hotels/travel/lebcy-courtyard-hanover-lebanon/ Courtyard by Marriott] (ten minute drive) || $145 || 603-643-5600
|}

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct If an incident occurs, please use the following contact information:

Conference organizers: 
Joe Montibello (cell) - 603-553-0393 
Dartmouth Safety & Security: 603-646-4000 
Hanover Police Department: 603-643-2222 
Grafton County Support Center Against Domestic Violence and Sexual Assault: 603-448-5922 

==Programming==
===Programming Sign-up===
Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a wiki account, you can contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Joe Montibello (joe@dartmouth.edu) to have your presentation/lightning talk/discussion topic added below for you.

====Presentations====
15-20 minutes talks.

# [[User:JulieSwierczek|Julie Swierczek]] - Digital Preservation for Everyone: A 15-Minute Romp through the OAIS Model
#
#

====Lightning Talks====
A lightning talk is a fast-paced, 5-minute talk on the topic of your choice.

#
#
#

====Discussion Topics====
List some topics you are interested in talking to others during breakout time.

# Digital Preservation: Tools, Workflows, Policies, the Good, the Bad, and the Ugly, etc.
#
#

===Topics of interest===
Prospective attendees shared these responses to the survey question "What topics would you like to see presented on?"

* Digital preservation workflows.
* Tools for improving information management capabilities
* Blacklight
* Digital preservation tools
* Data visualization
* Cyber security in libraries
* Any Alma shops using import profiles? How are people managing their e-resources on a large scale? What cool ways are people enriching their records with non-library metadata - how are they doing this technically and what cultural changes are necessary to gain approval - is this a project with a specific scope or part of ongoing enrichment?
* Discovery tool improvements, innovative ways to spotlight collections online
* DPLA MAP as local data model
* Bibframe and Drupal
* I'd like to explore a career as a systems librarian, and I would love it if someone did a presentation on "what I wish I had known before I became a systems librarian" or "what you need to know to be a systems librarian" or "a day in the life..." or some similar overview. I recognize that 'systems librarian' can mean a bazillion different things, but I'm sure a pro could get to the core of it. Also, this would be very newbie-oriented, so maybe it's not appropriate for this meeting. Still, it's just an idea.
* Open source coding and programming basics, archival description (EAD) tools and applications...
* Linked data, data visualization, repositories, discovery environments
* Linux, HTML5, Python, Javascript
* Blacklight, Solr, Library location service
* Video game design in libraries, particularly with teens; parallels between storytelling and video game design experiences.
* TEI, text/data mining
* Analytics, repository development, metadata enrichment, server administration, user interface testing results, complex RDF descriptive metadata modeling, etc.
* Publication workflows in libraries
* Digital humanities and archives, linked data, diversifying the profession(s), digital preservation and born digital materials
* Sustainability planning, digital scholarship for subject liaisons, project development, hands-on coding/tool sessions
* Linked open data
* Digital curation, digital preservation, digital scholarship, born-digital preservation, digital collections.
* Database and collections management-related such as open source technologies that can assist in these areas.
* Coding for preschoolers/early elementary students, coding in school libraries
* The potential of tech in libraries and beyond.
* Web design; user testing; learning resources for junior-level web developers
* Open source programs for collaborative writing, editing, and publishing. How to build on open source programs in your special area of interest. Programs and tools for data visualization. Programs and tools for digital exhibits. Programs for managing metrics. How to talk to programmers and software designers- how to explain your vision so the result is what was expected. What programs are most important for library staff to know about? Ruby on Rails, Python.....? The anatomy of a program.
* Advantages of non-digital approaches.
* Digital preservation approaches (such as variable media and crowdsourcing) and techniques (such as emulation), as well as strategies for teaching digital curation.
* Asynchronous storage strategies. Advanced search tools for repositories on the web. Indexing metadata with tools/products other than Solr. All the topics.
* Code for websites. RDF ontology for library and archives.

==Schedule==

===Friday, December 4===

Registration and coffee starts at 9 a.m. Program starts at 10 and continues through late afternoon/early evening. Further details TBA.

==Registration==
https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

==Mailing list==
NECode4Lib has a low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

NECode4lib 2015 Fall

2015-10-16T13:07:11Z

JulieSwierczek: added Digital Preservation topic

Please join us Friday, December 4, in Hanover, NH for the Fall 2015 NECode4Lib conference. This informal conference will feature sessions covering technology in libraries, archives and museums in the New England area.

===Location===
This NECode4Lib meeting will be hosted by the Dartmouth College Library.

'''When''' - Friday, December 4th

'''Where''' - Jones Media Center, [http://m.dartmouth.edu/map/campus?feed=f8a86d47cf&group=dartmouth&featureindex=65&category=f8a86d47cf%3A5&_b=%5B{%22t%22%3A%22Map%22%2C%22lt%22%3A%22Map%22%2C%22p%22%3A%22index%22%2C%22a%22%3A%22%22}%5D Baker-Berry Library], Dartmouth College

'''Registration Cost''' - Free!

'''Registration Link''' - https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

'''Planning Committee''' - Joe Montibello (joseph.montibello@dartmouth.edu), Jenny Mullins (jennifer.l.mullins@dartmouth.edu), Carla Galarza (carla.m.galarza@dartmouth.edu), Laura Braunstein (laura.r.braunstein@dartmouth.edu), Shaun Akhtar (shaun.y.akhtar@dartmouth.edu)

===Logistics===
====Transportation====
* Hanover is a few minutes' drive from Exit 18 on I-89 or Exit 13 on I-91.
* The private [http://dartmouthcoach.com/ Dartmouth Coach] provides bus service to Hanover from South Station and Logan Airport in Boston and from Midtown Manhattan in New York City.
* On-campus parking is available for $10/car. Please contact Shaun Akhtar (shaun.y.akhtar@dartmouth.edu) to make arrangements.
* We are also looking into helping arrange carpooling. More information will be distributed to registrants as we get closer to the event. Please contact Shaun at the address above with any questions.

====Hotels====
Hotel blocks are being held for the nights of Thursday, December 3 and Friday, December 4 under Code4Lib -- mention this event when calling to make your reservation. Hotel blocks will be held at these rates until November 3. For additional suggestions, or if you need to book housing after the blocks have expired (or if they have sold out), please email the organizers at Code4Lib@dartmouth.edu

{| class="wikitable"
|-
! Hotel !! Rate !! Phone
|-
| [http://www.hanoverinn.com/ Hanover Inn] (five minute walk from Baker-Berry Library) || $129 || 603-643-4300
|-
| [http://www.sixsouth.com/ Six South Street Hotel] (ten minute walk) || $114 || 603-643-0600
|-
| [http://www.elementhanoverlebanon.com/ Element Hotel] (ten minute drive) || $129 || 603-448-5000
|-
| [http://www.marriott.com/hotels/travel/lebcy-courtyard-hanover-lebanon/ Courtyard by Marriott] (ten minute drive) || $145 || 603-643-5600
|}

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct If an incident occurs, please use the following contact information:

Conference organizers: 
Joe Montibello (cell) - 603-553-0393 
Dartmouth Safety & Security: 603-646-4000 
Hanover Police Department: 603-643-2222 
Grafton County Support Center Against Domestic Violence and Sexual Assault: 603-448-5922 

==Programming==
===Programming Sign-up===
Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a wiki account, you can contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Joe Montibello (joe@dartmouth.edu) to have your presentation/lightning talk/discussion topic added below for you.

====Presentations====
15-20 minutes talks.

# Julie Swierczek - Digital Preservation for Everyone: A 15-Minute Romp through the OAIS Model
#
#

====Lightning Talks====
A lightning talk is a fast-paced, 5-minute talk on the topic of your choice.

#
#
#

====Discussion Topics====
List some topics you are interested in talking to others during breakout time.

# Digital Preservation: Tools, Workflows, Policies, the Good, the Bad, and the Ugly, etc.
#
#

===Topics of interest===
Prospective attendees shared these responses to the survey question "What topics would you like to see presented on?"

* Digital preservation workflows.
* Tools for improving information management capabilities
* Blacklight
* Digital preservation tools
* Data visualization
* Cyber security in libraries
* Any Alma shops using import profiles? How are people managing their e-resources on a large scale? What cool ways are people enriching their records with non-library metadata - how are they doing this technically and what cultural changes are necessary to gain approval - is this a project with a specific scope or part of ongoing enrichment?
* Discovery tool improvements, innovative ways to spotlight collections online
* DPLA MAP as local data model
* Bibframe and Drupal
* I'd like to explore a career as a systems librarian, and I would love it if someone did a presentation on "what I wish I had known before I became a systems librarian" or "what you need to know to be a systems librarian" or "a day in the life..." or some similar overview. I recognize that 'systems librarian' can mean a bazillion different things, but I'm sure a pro could get to the core of it. Also, this would be very newbie-oriented, so maybe it's not appropriate for this meeting. Still, it's just an idea.
* Open source coding and programming basics, archival description (EAD) tools and applications...
* Linked data, data visualization, repositories, discovery environments
* Linux, HTML5, Python, Javascript
* Blacklight, Solr, Library location service
* Video game design in libraries, particularly with teens; parallels between storytelling and video game design experiences.
* TEI, text/data mining
* Analytics, repository development, metadata enrichment, server administration, user interface testing results, complex RDF descriptive metadata modeling, etc.
* Publication workflows in libraries
* Digital humanities and archives, linked data, diversifying the profession(s), digital preservation and born digital materials
* Sustainability planning, digital scholarship for subject liaisons, project development, hands-on coding/tool sessions
* Linked open data
* Digital curation, digital preservation, digital scholarship, born-digital preservation, digital collections.
* Database and collections management-related such as open source technologies that can assist in these areas.
* Coding for preschoolers/early elementary students, coding in school libraries
* The potential of tech in libraries and beyond.
* Web design; user testing; learning resources for junior-level web developers
* Open source programs for collaborative writing, editing, and publishing. How to build on open source programs in your special area of interest. Programs and tools for data visualization. Programs and tools for digital exhibits. Programs for managing metrics. How to talk to programmers and software designers- how to explain your vision so the result is what was expected. What programs are most important for library staff to know about? Ruby on Rails, Python.....? The anatomy of a program.
* Advantages of non-digital approaches.
* Digital preservation approaches (such as variable media and crowdsourcing) and techniques (such as emulation), as well as strategies for teaching digital curation.
* Asynchronous storage strategies. Advanced search tools for repositories on the web. Indexing metadata with tools/products other than Solr. All the topics.
* Code for websites. RDF ontology for library and archives.

==Schedule==

===Friday, December 4===

Registration and coffee starts at 9 a.m. Program starts at 10 and continues through late afternoon/early evening. Further details TBA.

==Registration==
https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

==Mailing list==
NECode4Lib has a low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

NECode4lib 2015 Fall

2015-10-16T13:04:58Z

JulieSwierczek: /* Presentations */

Please join us Friday, December 4, in Hanover, NH for the Fall 2015 NECode4Lib conference. This informal conference will feature sessions covering technology in libraries, archives and museums in the New England area.

===Location===
This NECode4Lib meeting will be hosted by the Dartmouth College Library.

'''When''' - Friday, December 4th

'''Where''' - Jones Media Center, [http://m.dartmouth.edu/map/campus?feed=f8a86d47cf&group=dartmouth&featureindex=65&category=f8a86d47cf%3A5&_b=%5B{%22t%22%3A%22Map%22%2C%22lt%22%3A%22Map%22%2C%22p%22%3A%22index%22%2C%22a%22%3A%22%22}%5D Baker-Berry Library], Dartmouth College

'''Registration Cost''' - Free!

'''Registration Link''' - https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

'''Planning Committee''' - Joe Montibello (joseph.montibello@dartmouth.edu), Jenny Mullins (jennifer.l.mullins@dartmouth.edu), Carla Galarza (carla.m.galarza@dartmouth.edu), Laura Braunstein (laura.r.braunstein@dartmouth.edu), Shaun Akhtar (shaun.y.akhtar@dartmouth.edu)

===Logistics===
====Transportation====
* Hanover is a few minutes' drive from Exit 18 on I-89 or Exit 13 on I-91.
* The private [http://dartmouthcoach.com/ Dartmouth Coach] provides bus service to Hanover from South Station and Logan Airport in Boston and from Midtown Manhattan in New York City.
* On-campus parking is available for $10/car. Please contact Shaun Akhtar (shaun.y.akhtar@dartmouth.edu) to make arrangements.
* We are also looking into helping arrange carpooling. More information will be distributed to registrants as we get closer to the event. Please contact Shaun at the address above with any questions.

====Hotels====
Hotel blocks are being held for the nights of Thursday, December 3 and Friday, December 4 under Code4Lib -- mention this event when calling to make your reservation. Hotel blocks will be held at these rates until November 3. For additional suggestions, or if you need to book housing after the blocks have expired (or if they have sold out), please email the organizers at Code4Lib@dartmouth.edu

{| class="wikitable"
|-
! Hotel !! Rate !! Phone
|-
| [http://www.hanoverinn.com/ Hanover Inn] (five minute walk from Baker-Berry Library) || $129 || 603-643-4300
|-
| [http://www.sixsouth.com/ Six South Street Hotel] (ten minute walk) || $114 || 603-643-0600
|-
| [http://www.elementhanoverlebanon.com/ Element Hotel] (ten minute drive) || $129 || 603-448-5000
|-
| [http://www.marriott.com/hotels/travel/lebcy-courtyard-hanover-lebanon/ Courtyard by Marriott] (ten minute drive) || $145 || 603-643-5600
|}

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct If an incident occurs, please use the following contact information:

Conference organizers: 
Joe Montibello (cell) - 603-553-0393 
Dartmouth Safety & Security: 603-646-4000 
Hanover Police Department: 603-643-2222 
Grafton County Support Center Against Domestic Violence and Sexual Assault: 603-448-5922 

==Programming==
===Programming Sign-up===
Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a wiki account, you can contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Joe Montibello (joe@dartmouth.edu) to have your presentation/lightning talk/discussion topic added below for you.

====Presentations====
15-20 minutes talks.

# Julie Swierczek - Digital Preservation for Everyone: A 15-Minute Romp through the OAIS Model
#
#

====Lightning Talks====
A lightning talk is a fast-paced, 5-minute talk on the topic of your choice.

#
#
#

====Discussion Topics====
List some topics you are interested in talking to others during breakout time.

#
#
#

===Topics of interest===
Prospective attendees shared these responses to the survey question "What topics would you like to see presented on?"

* Digital preservation workflows.
* Tools for improving information management capabilities
* Blacklight
* Digital preservation tools
* Data visualization
* Cyber security in libraries
* Any Alma shops using import profiles? How are people managing their e-resources on a large scale? What cool ways are people enriching their records with non-library metadata - how are they doing this technically and what cultural changes are necessary to gain approval - is this a project with a specific scope or part of ongoing enrichment?
* Discovery tool improvements, innovative ways to spotlight collections online
* DPLA MAP as local data model
* Bibframe and Drupal
* I'd like to explore a career as a systems librarian, and I would love it if someone did a presentation on "what I wish I had known before I became a systems librarian" or "what you need to know to be a systems librarian" or "a day in the life..." or some similar overview. I recognize that 'systems librarian' can mean a bazillion different things, but I'm sure a pro could get to the core of it. Also, this would be very newbie-oriented, so maybe it's not appropriate for this meeting. Still, it's just an idea.
* Open source coding and programming basics, archival description (EAD) tools and applications...
* Linked data, data visualization, repositories, discovery environments
* Linux, HTML5, Python, Javascript
* Blacklight, Solr, Library location service
* Video game design in libraries, particularly with teens; parallels between storytelling and video game design experiences.
* TEI, text/data mining
* Analytics, repository development, metadata enrichment, server administration, user interface testing results, complex RDF descriptive metadata modeling, etc.
* Publication workflows in libraries
* Digital humanities and archives, linked data, diversifying the profession(s), digital preservation and born digital materials
* Sustainability planning, digital scholarship for subject liaisons, project development, hands-on coding/tool sessions
* Linked open data
* Digital curation, digital preservation, digital scholarship, born-digital preservation, digital collections.
* Database and collections management-related such as open source technologies that can assist in these areas.
* Coding for preschoolers/early elementary students, coding in school libraries
* The potential of tech in libraries and beyond.
* Web design; user testing; learning resources for junior-level web developers
* Open source programs for collaborative writing, editing, and publishing. How to build on open source programs in your special area of interest. Programs and tools for data visualization. Programs and tools for digital exhibits. Programs for managing metrics. How to talk to programmers and software designers- how to explain your vision so the result is what was expected. What programs are most important for library staff to know about? Ruby on Rails, Python.....? The anatomy of a program.
* Advantages of non-digital approaches.
* Digital preservation approaches (such as variable media and crowdsourcing) and techniques (such as emulation), as well as strategies for teaching digital curation.
* Asynchronous storage strategies. Advanced search tools for repositories on the web. Indexing metadata with tools/products other than Solr. All the topics.
* Code for websites. RDF ontology for library and archives.

==Schedule==

===Friday, December 4===

Registration and coffee starts at 9 a.m. Program starts at 10 and continues through late afternoon/early evening. Further details TBA.

==Registration==
https://www.eventbrite.com/e/ne-code4lib-tickets-18823486555

==Mailing list==
NECode4Lib has a low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

User:JulieSwierczek

2015-10-16T13:00:27Z

JulieSwierczek: added contact information

Julie Swierczek, Harvard Art Museums. julie_swierczek {at} harvard.edu. @JulieSwierczek on Twitter.

2016 Invited Speakers Nominations

2015-09-11T15:37:23Z

JulieSwierczek: Added Kate Heddleston

Nominations for invited speakers/keynotes for Code4Lib 2016 in Philadelphia. Please include a description and any relevant links and try to keep the list in alphabetical order.

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

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

</pre>

__TOC__

==Mike Bostock==
Interactive Graphic Design for The New York Times and the author of D3.js, a popular open-source library for visualizing data using web standards.

Prior to The New York Times, Mike was a visualization scientist for Square and a computer science PhD student at Stanford University. Mike received the BSE degree in computer science in 2000 from Princeton University.
ere's his [https://twitter.com/mbostock Twitter]; and his [http://bost.ocks.org/mike/ site]

== danah boyd ==
dana boyd is a Principal Researcher at Microsoft Research and the founder of [http://www.datasociety.net/ Data & Society Research Institute]. She's also a Visiting Professor at New York University's Interactive Telecommunications Program and a faculty affiliate at Harvard's Berkman Center. For over a decade, her research focused on how young people use social media, which resulted in two books: Hanging Out, Messing Around, and Geeking Out (2009) and It's Complicated (2014). More recently, she has focused on the social and cultural dimensions of big data, especially privacy and publicity, data(mis)interpretation, and the civil rights implications of data analytics. She often works closely with librarians, and was the keynote speaker at the Reference and User Services Association President’s Program at ALA Annual in San Francisco in 2015. Read more at [http://www.zephoria.org/thoughts/ her blog], on [https://twitter.com/zephoria Twitter], or read her [http://www.danah.org/papers/#essays Essays].

== Mandy Brown ==
Mandy Brown builds systems to help writers and editors to work together. She co-founded and served as CEO of [http://editorially.com/ Editorially], a platform for collaborative writing and editing; Editorially was acquired by Vox Media where she is now director of platform. She is also co-founder and was editor-in-chief of [http://abookapart.com/ A Book Apart], was a contributing editor for [http://alistapart.com/ A List Apart], and edited many books, including [http://shapeofdesignbook.com/ The Shape of Design], by Frank Chimero. She previously served as communications director and product lead at [http://typekit.com/ Typekit] and as creative director at [http://wwnorton.com/ W. W. Norton & Company]. She blogs at [http://aworkinglibrary.com/ A Working Library] and has spoken at [http://2014.dconstruct.org/ dConstruct], [http://2012.buildconf.com/ Build], [http://confab2011.com/ Confab], [http://typotalks.com/sanfrancisco/ TYPO SF], and [http://2013.beyondtellerrand.com/ Beyond Tellerrand ]. Additionally, [http://aworkinglibrary.com/coffee/ she mentors and advises people from underrepresented groups in the tech industry]. She lives in Philadelphia.

== Kimberly Bryant ==
Kimberly Bryant is a Biotechnology/Engineering professional who founded [http://www.blackgirlscode.com/ BlackGirlsCode] in 2011, to meet the needs of young women of color who are underrepresented in the currently exploding field of technology. Bryant received her first taste of computer programming when Fortran and Pascal were still the popular languages in the computing world and the 'Apple Macintosh' was the new kid on the block. Much has changed since those days and the mission of BlackGirlsCode is to introduce programming and technology to a new generation of coders (girls aged 7 - 17) who will become the leaders and creators of tomorrow.

== Maciej Cegłowski ==
Maciej Cegłowski, is a programmer, [http://idlewords.com/art/ painter], [http://www.idlewords.com/ essayist], [https://www.kickstarter.com/projects/431908798/send-idle-words-to-antarctica travel writer], and [http://idlewords.com/talks/ speaker]. He has been running Pinboard, a bookmarking site, since 2009. He has worked at Yahoo!, the Andrew W. Mellon Foundation, and the National Institute for Technology and Liberal Education, and has done contract work for Twitter and SixApart. He's funny on Twitter, whether he's representing [https://twitter.com/baconmeteor himself] or his company, [https://twitter.com/pinboard Pinboard].

== Aaron Straup Cope ==
Aaron Straup Cope is a software developer who believes that "promise of the Internet is to be a bridge for cross-pollinating peoples, ideas and communities"[1] and his work shows it. Currently at [https://mapzen.com/ Mapzen] he is building a [http://whosonfirst.mapzen.com/ Who's On First], a gazetteer of places "each with a stable identifier and some number of descriptive properties about that location." Previously he designed and developed the much lauded [http://collection.cooperhewitt.org collections website] for the Cooper-Hewitt Museum. His work consistently focuses on publishing data to the web with stable identifiers, while eschewing much of the formality and overhead of "Linked Data", a point he made quite clearly in his talk [http://mw2015.museumsandtheweb.com/proposal/omgwtftgn/ "OMGWTFTGN"] at Museums and the Web 2015, where he asked if releasing a 17GB RDF dataset is really the best way to get data used by... anyone. Read [http://www.aaronstraupcope.com/resume/en/aaronstraupcope-resume-en.txt Aaron Straup Cope's resume] for more information.

== Brigitte Daniel ==
Brigitte Daniel is a digital access advocate with experience in telecommunications and social entrepreneurship.

In May 2006, she became the executive vice president of Wilco Electronic Systems, a small telecommunications firm founded in 1977 by her father that has primarily done installations for the Philadelphia Housing Authority.

In that role, she became a frequent speaker on digital divide and web literacy issues, particularly in the Philadelphia technology community. She was part of the 2011 class of Eisenhower Fellows. Read more from her on [https://twitter.com/brigittedaniel Twitter].

== Catherine Farman ==
Philadelphian Catherine Farman is a developer, a Technology & Innovation Fellow Consumer Finance Protection Bureau, and a self-described "responsive design fanatic, feminist, Chicana, Texpat, cat lady, and teacher at [https://www.girldevelopit.com/chapters/philadelphia Girls Develop It's Philadelphia Chapter]"; she recently left HappyCog (the prestigious studio founded by A List Apart's Jeffrey Zeldman). More information on Catherine Farman is available at [http://cfarman.com/ her website, cfarman.com], and on [https://twitter.com/cfarm Twitter], and several of her recent speeches are listed on [http://lanyrd.com/profile/cfarm/past/speaking/ Lanyrd], though absent from that list is her 2014 presentation at OSCON, "[https://www.safaribooksonline.com/library/view/oscon-2014-complete/9781491910795/part96.html Lessons from Girl Develop It: Getting More Women Involved in Open Source]" (link goes to a video of the talk, which she co-presented with Corinne Warnshuis, Girls Develop It's excutive director).

== Paul Ford ==
Paul Ford is a Brooklyn-based writer and web technologist. He often writes about [https://medium.com/message/how-paper-magazines-web-engineers-scaled-kim-kardashians-back-end-sfw-6367f8d37688 the web], [http://www.npr.org/templates/story/story.php?storyId=6241967 archives] [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ programming], [http://www.ftrain.com/wwic.html the nature of information], and [https://medium.com/message/networks-without-networks-7644933a3100 living in the information age]. Past projects include [https://medium.com/message/tilde-club-i-had-a-couple-drinks-and-woke-up-with-1-000-nerds-a8904f0a2ebf tilde.club] and the [http://www.ftrain.com/AWebSiteForHarpers.html semantic web-ified harpers.org] (back in 2003). His ~30,00-word article [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ What Is Code?] was the entire June 11, 2015 issue of Bloomberg BusinessWeek. Learn more at his [http://ftrain.com website], on [http://twitter.com/ftrain Twitter], or on [https://medium.com/@ftrain Medium], or watch [https://www.youtube.com/watch?v=WSL5qVL3Mng his talk at XOXO 2014] or [http://www.bloomberg.com/news/videos/2015-06-12/-what-is-code-charlie-rose-06-12- his interview on Charlie Rose]. He was also interviewed at [http://www.inthelibrarywiththeleadpipe.org/2012/an-interview-with-paul-ford-and-gina-trapani/ at In the Library with the Lead Pipe, along with Gina Trapani].

== Sorelle Friedler ==
"Algorithms are already being used to make decisions that affect people's lives and livelihoods, and this trend is only increasing," [https://www.haverford.edu/college-communications/news/sorelle-friedler-studies-programming-and-prejudice says Sorrelle Friedler]. "Often, one of the selling points of using an algorithm is that it will be less biased than the current human process. While it is possible to create algorithms that reduce bias, the use of an algorithm does not on its own guarantee that. It's important that computer scientists, as well as policymakers, understand the limitations and work to make algorithmic decisions fair."

Sorelle Friedler has been an Assistant Professor of Computer Science at Haverford College since 2014 and was visiting at Haverford starting in 2012 (Haverford is just a few miles from Philadelphia). Her research interests include the design and analysis of algorithms, computational geometry, data mining and machine learning, and the application of such algorithms to interdisciplinary data. She is a [http://www.datasociety.net/updates/featured/announcements/2015/03/introducing-2015-2016-fellows-class/ 2015-2016 Fellow at the Data & Society Research Institute] for her work on preventing discrimination in machine learning. Learn more about her work on her [http://ww3.haverford.edu/computerscience/faculty/sorelle/index.php Haverford Computer Science page].

== Brett Anitra Gilbert ==
"I’ve been doing research in Johannesburg, South Africa, to understand what the city needs to do to better support technology entrepreneurs," [http://www.business.rutgers.edu/news/faculty-insights-professor-brett-gilbert-looks-how-tech-clusters-emerge-cities says Rutgers Business School professor Brett Gilbert]. "The city is actively in the process of trying to see a tech cluster emerge, so my research is intended to help them understand what needs to happen in order to see a tech community thrive in Johannesburg. It's research I’m doing concurrently in Newark, New Jersey, because the city would like to see a technology community emerge here. The research is really comparing the process these two cities are going through. Most research on clusters focuses on clusters that already exist and on regions that are somewhat well established so you don’t see a lot that helps people understand what a city or region would need to do if they want to see one of these technology clusters emerge."

Dr. Gilbert's dissertation, "[http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1371727 The Implications of Geographic Cluster Locations for New Venture Performance]" was awarded a Kauffman Dissertation Fellowship in 2004, and selected as a finalist for the Entrepreneurship Division's 2005 Heizer Award for outstanding dissertations in entrepreneurship. In addition to examining emerging technology communities in developing market contexts, she is also focusing on understanding emerging "clean energy" technologies. She has taught a variety of entrepreneurship courses on creativity and innovation, and the startup and management of new ventures. At RBS, Dr. Gilbert teaches the Technology Ventures course for undergraduates and graduates, and the Ph.D. seminar in entrepreneurship. Learn more on [https://twitter.com/ProfGilbert Twitter] and on [http://www.business.rutgers.edu/faculty-research/directory/gilbert-brett her page at the Rutgers Business School website].

== Amelia Greenhall ==
Amelia Greenhall is the Chief Creative Officer of [http://magicvibes.co/ Magic Vibes Corporation]. Previously, she cofounded and served as Executive Director and board chair of [http://doubleunion.org/ Double Union], a non-profit feminist hacker/maker space in San Francisco with the mission of being a safe and comfortable space for women to work on their projects. She also cofounded the publication Model View Culture, and designed things for companies including [http://futureadvisor.com/ FutureAdvisor] and [http://www.ameliagreenhall.com/pieces/budge Habit Labs]. She is the publisher of the [http://openreviewquarterly.com/ Open Review Quarterly] literary journal, and the entries at [http://ameliagreenhall.com/blog her personal blog] are usually made available as episodes of [http://ameliagreenhall.com/pieces/amelia-explains-it-all Amelia Explains It All], a "podcast for men in tech."

== Kate Heddleston ==
Kate Heddleston is a software engineer who mostly works on Python projects. She has been a mentor for Hackbright Academy and PyLadies. She blogs and gives talks about how our engineering environments are killing diversity (see [https://kateheddleston.com/talk/ea142cd2-f026-4615-ab90-2170f06c739b her talk] and [https://kateheddleston.com/blog/how-our-engineering-environments-are-killing-diversity-introduction her blog series]), on [https://kateheddleston.com/talk/ef464595-b113-4c1b-9c5b-cc1f3681055c technical onboarding, training, and mentoring], and on the [https://kateheddleston.com/blog/a-modern-day-take-on-the-ethics-of-being-a-programmer ethics of being a programmer], among other topics. Here is her [https://kateheddleston.com/ website].

== Andrew Hoppin ==
Andrew Hoppin is the co-founder and president of [http://nucivic.com NuCivic], a technology innovator, and open source advocate. An Ex-NASA scientist who brings his theories of collaboration, open-source technologies to create open civic platforms. As president of NuCivic, his mission is to improve the efficacy of civic organizations and governments, by making innovative knowledge management solutions accessible. Namely Nucivic's DKAN open data platform DKAN provides an open source solution for government organizations, libraries and civic organizations for data cataloging, publishing and visualizing.
Andrew was awarded the 2010 New York State Public Sector CIO of the Year by GovTech Magazine, and was named one of the top 50 government CIOs in the United States by Information Week magazine, for his successful effort to deploy the first major New York State government website, NYSenate.gov, which won “Best of New York” awards for Project Excellence.

== Helen Horstmann-Allen ==
Pobox.com promised its customers a lifetime email address, and found a loyal following immediately. In addition to email addresses and accounts, their customers requested reliable email-based discussion forums, mailing lits, and newsletters, so they created Listbox.com. Philadelphian Helen Horstmann-Allen has been president of IC Group, the home of Pobox.com and Listbox.com, since 2000; prior to that, she was its director of operations, and she's been in charge of Pobox.com since 1997. She's in love with Philadelphia and food -- thus [http://phillyfoodie.com/ Philly Foodie] -- and can be found on [https://twitter.com/philliefoodie Twitter], too.

== Jess Klein ==
Open Web Designer at Bocoup

If you ask about her passions, Jess will draw you a venn diagram with the words community, freedom, and learning, and point to the sweet spot where all three overlap. She is dedicated to connecting people and ideas through new technologies and interactive experiences. Before Bocoup, Jess worked at the Mozilla Foundation, where she served as Creative Lead for such projects as the X-Ray Goggles, Hackasaurus (which became part of the larger Webmaker platform), Thimble and the Hive. She also served as the Creative Director for Mozilla Open Badges, where she helped develop an ecosystem of tools for learners to earn, assess, issue and display digital micro-credentials. A Rockaway Beach native, Jess co-founded Rockaway Help in the wake of Hurricane Sandy to empower the community to find solutions for emergency response, preparedness and rebuilding through hyperlocal open news and the development of innovative community-designed technologies. She was named a White House Champion of Change for her civic hacktivism. Here is her [http://jessicaklein.com/ website].

== Kate Krauss ==

Kate Krauss is the Director of Communications and Public Policy for the Tor Project, a nonprofit organization that builds free, online privacy tools that allow users to defy shoe companies and intelligence agencies alike while they stay free and anonymous on the internet. As a human rights advocate, Kate lead several successful campaigns to free public health experts and human rights activists who were imprisoned in China. She became interested in internet freedom when she sought help from San Francisco hackers to aid a well-known Chinese health advocate whose huge, popular web site for people with hepatitis had been taken down by the Chinese government.

Prior to her work in online privacy, she served as Executive Director of the AIDS Policy Project, where she lead a successful effort to move $35 million into cure research at the US National Institutes of Health and wrote groundbreaking reports that showed for the first time how little the world was investing in the search for a cure for AIDS. Kate has been chosen twice as one of the Poz 100, one of the top 100 people working in AIDS in the world. She was a very early member of the renowned AIDS activist group ACT UP. She has also spoken at several hacker conferences, including Chaos Communications Congress, where she delivered a talk on how mass surveillance in China was converted into political repression.

(However--*has* a sense of humor!)

== Alison Macrina ==
Alison Macrina is the founder and director of the Library Freedom Project (LFP), an initiative that helps libraries fulfill the the promise of intellectual freedom by teaching librarians and their local communities about surveillance threats, privacy rights and law, and privacy-protecting technology tools that help safeguard digital freedoms. She is passionate about connecting surveillance issues to larger global struggles for justice, demystifying privacy and security technologies for ordinary users, and resisting an internet controlled by a handful of intelligence agencies and multinational corporations. She cowrote the Radical Reference Collective’s zine, "[http://radicalreference.info/content/we-are-all-suspects-guide-people-navigating-expanded-powers-surveillance-21st-century We Are All Suspects]," which gives advice and tools for preventing surveillance, and has written or co-written articles for [http://boingboing.net/2014/09/13/radical-librarianship-how-nin.html Boing Boing] and [http://www.slate.com/blogs/future_tense/2014/10/20/adobe_s_digital_editions_e_book_software_and_library_patron_privacy.html Slate]. LFP has been featured in [https://libraryfreedomproject.org/press/ numerous prominent publications], including [http://www.thenation.com/article/librarians-versus-nsa/ The Nation] magazine and NPR's [http://www.onthemedia.org/story/librarians-vs-patriot-act/ On the Media], and LFP's partners include the Electronic Frontier Foundation, the American Civil Liberties Union, the Freedom of the Press Foundation, and the Tor Project.

In February 2015, LFP won a ~$250,000 two-year grant through the Knight Foundation’s News Challenge, which enabled her to work on LFP full-time. Prior to that, she was the technology librarian/IT manager at the Watertown (Massachusetts) Free Public Library.

== Katrina Owen ==
Katrina Owen is the creator of [http://exercism.io/exercism exercism], a FLOSS project that supports students who are learning to code by giving them practice problems and real world feedback. Exercises are currently available in Clojure, CoffeeScript, C++, C#, Emacs Lisp, Elixir, Erlang, F#, Go, Haskell, Java, JavaScript, Lisp Flavoured Erlang (LFE), Common Lisp, Lua, Objective-C, OCaml, Perl 5, PHP, PL/SQL, Python, Ruby, Rust, Scala, Scheme, and Swift, and exercism developers are in the process of adding ECMAScript, Groovy, Nimrod, Perl 6, Pony, Racket, Standard ML, and VB.NET. Katrina Owen is herself a polyglot developer and Ruby Hero award winner who has spoken at numerous conferences; example talks include: [http://confreaks.tv/videos/lonestarruby2013-keynote-hacking-passion Hacking Passion]; [https://www.youtube.com/watch?v=GWEEPt8VvmU Overkill]; [http://confreaks.tv/videos/bathruby2015-here-be-dragons Here Be Dragons]; and [http://confreaks.tv/videos/cascadiaruby2012-therapeutic-refactoring Therapeutic Refactoring]. She accidentally became a developer while pursuing a degree in molecular biology, and began nitpicking code in 2006 while volunteering at JavaRanch. When programming, her focus is on automation, workflow optimization, and refactoring. She is passionate about open source and contributes to several projects outside of exercism. Learn more on [https://github.com/kytrinyx GitHub] and [https://twitter.com/kytrinyx Twitter].

== Lauren Pressley ==
Lauren Pressley became the University of Washington Tacoma Library Director and Associate Dean of University Libraries on September 15, 2015. Her professional interests include formal and informal learning, design in library services, the evolving information environment, organizational change, and the future of libraries. She is the author of [https://unglue.it/work/76348/ So You Want to Be a Librarian] and [http://www.alastore.ala.org/detail.aspx?ID=3969 Wikis for Libraries], a co-chair of [https://www.librarypipeline.org/ Library Pipeline], and holds an elected position on the American Library Association Council. She has also served on the Library Information Technology Association board of directors and the [http://www.nmc.org/nmc-horizon/ Horizon Project] advisory board.

Prior to joining UW, she was the Director of Learning Environments and Associate Professor at Virginia Tech University Libraries, where she led a team of thirty people who were responsible for enhancing situated learning by connecting services and spaces, including Reference, Circulation, Roving Services, Learning Spaces, Online Learning, academic programming, and community engagement. [http://www.slideshare.net/laurenpressley/presentations Several dozen of her presentations] are posted online.

== Aliya Rahman ==
Tech and social justice activist. Engineer. Read more at [http://www.techrepublic.com/article/aliya-rahman-former-code-for-progress-director-tech-and-social-justice-activist-martial-artist/ Tech Republic] and on [https://twitter.com/AliyaRahman Twitter]. From her [http://codeforprogress.org/app/program_director/ Code for Progress bio]:

<blockquote>
As Program Director, Aliya Rahman leads the recruitment, in-residence training, and job placement of Code for Progress fellows into full-time developer positions. Her work is informed by a background in legislative, electoral, and community organizing for racial and economic justice campaigns, and by a former life in public higher education conducting curriculum research and teaching computer programming and educational foundations/policy.

Aliya is the former Field Director of Equality Ohio, where she built a statewide field program focused on bridging gaps between racial justice organizers, LGBT rights groups, and labor. Prior to that, she worked for the Center for Community Change, first as their Ohio organizer in the passage of employment legislation supporting formerly incarcerated people, and later as a national circuit rider working with immigrant rights groups on voter engagement.

Aliya has developed Django applications, conducted tech trainings, or performed data analysis and targeting for every campaign, nonprofit, and university she has ever worked for - despite none of those tasks explicitly appearing on her job descriptions. Now based in Washington, DC, she is thoroughly enjoying life as a non-accidental techie, and is grateful to be part of an active ecosystem of women and people of color who believe tech has a pivotal role to play in creating social change.
</blockquote>

== Jenica Rogers ==
Jenica Rogers is Director of Libraries at the State University of New York at Potsdam. Her current professional interests include interrogating the ways our information economy is breaking down and reforming now that the internet changed everything, figuring out what the role of a library is in a reality in which warehousing books is sort of passé, and informing, mentoring, and supporting new library professionals as they hit the real world face first and at full speed. She has written at length about library issues on her blog, [http://www.attemptingelegance.com Attempting Elegance], represented SUNY Potsdam as the subject of [http://chronicle.com/article/As-Chemistry-Journals-Prices/134650/ an article in the Chronicle of Higher Education about journal prices], and has given numerous invited keynote speeches at library conferences around the United States, Canada, Australia, and New Zealand. In 2014, she was chosen to receive the American Library Association’s ALCTS HARRASSOWITZ Award for Leadership in Library Acquisitions.

To get a sense of her presentation style, watch her deliver the [https://www.youtube.com/watch?v=5vy0Kv4eqeg plenary speech at the 2013 Charleston Conference] (in which she discusses her refusal to pay the extortionate fees being charged by a professional association for its journals) as well as [https://www.youtube.com/watch?v=PhMXClsue9w the Vision speech at NASIG's 2014 Annual Conference].

== Jenn Schiffer ==
[http://jennmoney.biz/ Jenn Schiffer] ([https://twitter.com/jennschiffer Twitter]), aka jennmoneydollars, is an open web engineer at [http://bocoup.com/ Bocoup] and lives in New Jersey (a relatively easy commute from Philadelphia). She's good at making art with code and great at telling jokes. She was previously a senior front-end developer for the National Basketball Association and, before that, taught and evaluated computer science education at Montclair State University, her alma mater (BS and MS in Computer Science). She also organizes JerseyScript, a developer meetup based in New Jersey, which is just one of several ways she's working to attract and retain more people in the web development community. She's made a lot of [http://jennmoney.biz/talks/ recent podcast appearances and presentations at conferences].

== Cecily Walker ==
Cecily Walker is the Assistant Manager for Community Digital Initiatives & eLearning at Vancouver Public Library. In addition to her work on user experience and open data, she is an experienced speaker (keynoting DLF Forum this year) and has hosted a Twitter chat for first-generation library professionals (#L1S). Learn more at [http://cecily.info/ her website], and on [https://twitter.com/skeskali Twitter], [https://github.com/skeskali GitHub], and [http://www.inthelibrarywiththeleadpipe.org/about/editorial-board/cecily-walker/ In the Library with the Lead Pipe] (she is a member of the editorial board).

== Audrey Watters ==
Audrey Watters is an education writer with a focus on ed-tech. She is the author of [http://monsters.hackeducation.com/ The Monsters of Education Technology], a collection of her lectures, and she is currently working on two more books, [http://teachingmachin.es/ Teaching Machines] and [http://reclaim.hackeducation.com/ Claim Your Domain], both due out in 2015. She created [http://hackeducation.com/ Hack Education] in June 2010 shortly after she became a technology journalist because she was frustrated by the lack of coverage of education technology. Hack Education was always intended to be the sort of publication that she would want to read: smart and snarky, free of advertising and investor influence, and focused on tracking new technologies but not just because of some hyperbolic "revolution." Read more on [http://audreywatters.com/ her website], on [https://twitter.com/audreywatters Twitter], and on [https://github.com/audreywatters GitHub].

== Gabriel Weinberg ==
Gabriel Weinberg is the CEO and Founder of [https://duckduckgo.com/ DuckDuckGo], "the search engine that doesn't track you," and the co-author of [http://tractionbook.com/ Traction], "the book that helps startups get customers." He is also an active [https://angel.co/yegg/syndicate/ angel investor], and he lives and works in the Philadelphia suburbs. Learn more on [http://ye.gg/app/twitter Twitter] and [http://ye.gg/app/medium Medium], read [http://www.inthelibrarywiththeleadpipe.org/2010/marketing-search-an-interview-with-pete-bell-of-endeca-and-gabriel-weinberg-of-duckduckgo/ an interview with him (and Endeca co-founder Pete Bell) at In the Library with the Lead Pipe], or watch [https://vimeo.com/68099450 his speech at Gel 2013] or his [https://www.youtube.com/watch?t=59&v=TvfGJgzBeH0 appearance on Conversations with Great Minds].

== David Weinberger ==
David Weinberger, Ph.D., is one of the world's most respected thought leaders at the intersection of technology, business, and society. His latest book, [http://www.toobigtoknow.com/ Too Big to Know: Rethinking Knowledge Now That the Facts Aren't the Facts, Experts Are Everywhere, and the Smartest Person in the Room Is the Room], is a roadmap on taking advantage of networked knowledge now that it has replaced books and experts of old. He also is the author of [http://www.everythingismiscellaneous.com/ Everything Is Miscellaneous: The Power of the New Digital Disorder], which charts how as business, politics, science, and media move online, the rules of the physical world—in which everything has a place—are upended, as well as the critically acclaimed book [http://smallpieces.com/index.php Small Pieces Loosely Joined], a highly original and accessible reflection on the impact of the Internet on human behavior. He earned his doctorate in philosophy from the University of Toronto and taught philosophy for five years at New Jersey's Stockton State College. Since 2004, he has been a fellow at Harvard University's prestigious Berkman Center, gag writer for Woody Allen, NPR commentator for "All Things Considered" and "Here and Now," technology columnist for KMWorld and Darwin Magazine, blogging pioneer, and dot-com entrepreneur. [http://www.apbspeakers.com/speaker/david-weinberger This site has information on how to book him], and you can read more on [https://twitter.com/dweinberger Twitter] or on [http://www.hyperorg.com/blogger/ his blog].

== Brock Whitten ==
Making front-end development easier by the second. Co-creator of Surge, Harp, and Cordova/PhoneGap. Mozilla-WebFWD Alumni and advocate of a free and open web. A friend of the community. Read about Surge [https://surge.sh/tour here] and [https://medium.com/surge-sh/introducing-surge-the-cdn-for-front-end-developers-b4a50a61bcfc here].
Here is [http://sintaxi.com/ Brock's website]

== Kam Woods ==
Research Associate & Adjunct Faculty at University of North Carolina at Chapel Hill.

Kam is currently developing modified open source digital forensics tools for digital archivists. He works with archivists, librarians, forensics researchers, and other development groups to identify core needs in analyzing and preparing digital content for preservation -- specifically needs that can be addressed using existing high-performance forensic technologies (with a little tweaking). He is also interested in developing datasets and teaching technologies to support education and professional training in digital archiving. He gave a great talk at 2014 ALA, and I bet he would have some great tech and social insights for Code4Lib. Read more at [http://www.digpres.com/ Kam Woods's website].

== Jeffrey Zeldman ==
HappyCog/A List Apart (Philly/NYC-based)

Dubbed “King of Web Standards” by Business Week, Jeffrey Zeldman founded and is chairman of Happy Cog™ and has published A List Apart Magazine “for people who make websites” since 1998. He has written two books, notably the foundational text, Designing With Web Standards,currently in a 3rd Edition coauthored with Ethan Marcotte. It has been translated into 15 languages and is credited with converting the web design industry from tag soup and Flash to semantics and accessibility.
[http://happycog.com/zeldman Zeldman's page] on HappyCog.com.

== Kortney Ryan Ziegler ==
Founder, Trans*H4CK

Kortney Ryan Ziegler is an award winning artist, writer, and blogger based in Oakland, California. Dr. Ziegler is the first person to hold the Ph.D. of African American Studies from Northwestern University.

Dr. Ziegler is the founder of [http://www.transhack.org/ Trans*H4CK]--the only tech event of its kind that brings visibility to trans* tech innovators and entrepreneurs.

He is also the director of the multiple award winning documentary, [http://www.stillblackfilm.org/ STILL BLACK: a portrait of black transmen], runs the GLAAD Media Award nominated blog, [http://blackademic.com/ blac (k) ademic], and in 2013, was named one of the Top 40 Under 40 LGBT activists by The Advocate Magazine and one of the most influential African Americans by TheRoot100. Dr. Ziegler gave the closing keynote at the 2014 Annual LITA Forum in Albuquerque, New Mexico.

[[Category:Code4Lib2016|Invited Speakers Nomination]]
[[Category:Code4Lib Keynotes]]

2015 Preconference Proposals

2015-01-23T19:58:03Z

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

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

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

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

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

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

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

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

''Interested in Attending''
# Megan Kudzia
# Julie Swierczek

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===FULL DAY:===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

''Interested in Attending''
#Vicky Steeves

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2015-01-23T19:57:21Z

JulieSwierczek: /* Coding Custom Solutions for Every Department in the Library with File Analyzer */

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

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

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

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

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

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

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

''Interested in Attending''
# Megan Kudzia
# Julie Swierczek

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===FULL DAY:===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

''Interested in Attending''
#Vicky Steeves

[[Category:Code4Lib2015]]