Code4Lib - User contributions [en]

2025 Keynote Speakers Nominations

2024-11-12T20:12:36Z

Kayiwa: clean up cruft

Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.

'''Nominations will close after November 21, 2024.'''

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

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

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

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

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

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

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

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Hardy Pottinger at [mailto:hardy.pottinger@ucsf.edu?Subject=CODE4LIB%20KEYNOTE%20NOMINATION hardy.pottinger@ucsf.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

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

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

</pre>

__TOC__

==Cory Doctorow==

Cory is a great speaker, and he is brilliant. He bridges the worlds of learning, technology, ethics, and sanity. He embraces the dystopian without being maudlin.
Doctorow married Alice Taylor in October 2008, and they have a daughter named Poesy Emmeline Fibonacci Nautilus Taylor Doctorow, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.

[https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]

[https://pluralistic.net pluralistic.net]

[https://craphound.com craphound.com]

[https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]
... and many more.

He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]

==Molly White==

From [https://www.mollywhite.net/ Molly's website]:

I research and write critically about the cryptocurrency industry and technology more broadly in the [https://www.citationneeded.news/ Citation Needed] newsletter. I also run the websites [https://www.web3isgoinggreat.com/ Web3 is Going Just Great], where I highlight examples of how cryptocurrencies, web3 projects, and the industry surrounding them are failing to live up to their promises, and [https://www.followthecrypto.org/ Follow the Crypto], where I track cryptocurrency industry spending in the 2024 election cycle. I spend a lot of time thinking about how to make a better, more human-centered web, and am a passionate advocate for free and open access, digital sovereignty, and ethical technology.

I regularly speak to journalists and do media appearances. I also have given talks and guest lectures, and have advised policymakers and regulators in and outside of the United States.

Before veering into spending so much of my time thinking about cryptocurrency and its implications for the web and society, I was a professional software engineer.

I have also been an active editor of the English Wikipedia for over fifteen years, where I edit under the username [https://en.wikipedia.org/wiki/User:GorillaWarfare GorillaWarfare]. I am an administrator and [https://en.wikipedia.org/wiki/Wikipedia:Functionaries functionary], and previously served three terms on the [https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee Arbitration Committee]. I care deeply about free and open access to high-quality information, and view projects like Wikipedia as critical infrastructure.

Not from Molly's website:

Molly has intelligent takes on issues of concern to Code4Lib. For example, here's her take on Controlled Digital Lending: [https://www.citationneeded.news/hachette-v-internet-archive/ Big publishers think libraries are the enemy]. She is likely to enjoy and learn from Code4Lib as we enjoy and learn from her.

She can be reached at [molly@mollywhite.net]

==Anne Washington==

Dr. Washington is a public interest technologist and professor of data policy at the NYU Steinhardt school. Her expertise on public sector information currently addresses the emerging governance needs of data science. She has an undergraduate degree in computer science, an MLIS, and a PhD in information systems. She's worked at the Library of Congress and is the Advisory Boards of the Electronic Privacy Information Center (EPIC) and the Open Government Foundation.

[https://annewashington.com/ web site]

[mailto:anne.washington@nyu.edu email address]

==Nikki Stevens==

Dr. Stevens is a faculty associate at Arizona State, maintainer of the [https://github.com/drnikki/open-demographics Open Demographics] project, and past postdoctoral researcher at MIT, in the [https://dataplusfeminism.mit.edu/ Data + Feminism Lab]. Formerly a software engineer, she studies how software engineering is situated in systems of power -- for instance, the ways that relational database architecture dovetails with carceral logics. She says "if you invite me for a talk (hint hint), I would give talks titled:

* “Abolitionist Data Practices: Applying political goals to data structures”
* “Is my database racist? How white supremacy structures our databases”
* “The history of data modeling” (this one is more exciting than it sounds, I swear!)
* “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”

[https://nikkistevens.com/ personal web site]

[mailto:nikki.stevens@asu.edu email]

==Cat Hicks==

Dr. Hicks is a psychologist studying developer thriving. Her social science research includes learning cultures, code review anxiety, and the psychological affordances of organizations. She says "I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity." I think we would be interested in her research, and she would also be interested in code4lib's overlap with and differences from industry tech culture.

[https://www.drcathicks.com/ web site]

[https://mastodon.social/@grimalkina mastodon]

[https://www.changetechnically.fyi/ podcast]

==Meredith Martin==

As Director of the Center for Digital Humanities at Princeton, she has pioneered interdisciplinary initiatives, fostering collaboration across departments and institutions worldwide. She co-chairs the Artificial Intelligence + Digital Humanities special interest group for the Association for Computers and the Humanities and is an editor of the Journal of Cultural Analytics. As Director of the Center for Digital Humanities at Princeton University, Professor Martin is a leading expert on the intersection of technology and the humanities. Her innovative work, including the Princeton Prosody Archive and forthcoming Poetry’s Data, explores how technologies like natural language processing and machine learning can transform humanities research. Professor Martin would provide a thought-provoking keynote, sparking meaningful discussions about the evolving role of technology in academia and beyond.

CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]

[mailto:mm4@princeton.edu Meredith Martin]

[https://www.dariah.eu/2024/10/17/meredith-martin-cdh-faculty-director-discusses-the-evolution-of-the-humanities-engagement-with-data-at-the-dariah-annual-event/ DARIAH EU]

==Jane Doe (example)==

Jane works at ________, doing _______.

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

[mailto:jane@nowhere.foo janes_email_address]

2025 Keynote Speakers Nominations

2024-11-12T20:06:49Z

Kayiwa: add Meredith Martin

Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.

'''Nominations will close after November 21, 2024.'''

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

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

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

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

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

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

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

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Hardy Pottinger at [mailto:hardy.pottinger@ucsf.edu?Subject=CODE4LIB%20KEYNOTE%20NOMINATION hardy.pottinger@ucsf.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

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

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

</pre>

__TOC__

==Cory Doctorow==

Cory is a great speaker, and he is brilliant. He bridges the worlds of learning, technology, ethics, and sanity. He embraces the dystopian without being maudlin.
Doctorow married Alice Taylor in October 2008, and they have a daughter named Poesy Emmeline Fibonacci Nautilus Taylor Doctorow, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.

[https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]

[https://pluralistic.net pluralistic.net]

[https://craphound.com craphound.com]

[https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]
... and many more.

He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]

==Molly White==

From [https://www.mollywhite.net/ Molly's website]:

I research and write critically about the cryptocurrency industry and technology more broadly in the [https://www.citationneeded.news/ Citation Needed] newsletter. I also run the websites [https://www.web3isgoinggreat.com/ Web3 is Going Just Great], where I highlight examples of how cryptocurrencies, web3 projects, and the industry surrounding them are failing to live up to their promises, and [https://www.followthecrypto.org/ Follow the Crypto], where I track cryptocurrency industry spending in the 2024 election cycle. I spend a lot of time thinking about how to make a better, more human-centered web, and am a passionate advocate for free and open access, digital sovereignty, and ethical technology.

I regularly speak to journalists and do media appearances. I also have given talks and guest lectures, and have advised policymakers and regulators in and outside of the United States.

Before veering into spending so much of my time thinking about cryptocurrency and its implications for the web and society, I was a professional software engineer.

I have also been an active editor of the English Wikipedia for over fifteen years, where I edit under the username [https://en.wikipedia.org/wiki/User:GorillaWarfare GorillaWarfare]. I am an administrator and [https://en.wikipedia.org/wiki/Wikipedia:Functionaries functionary], and previously served three terms on the [https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee Arbitration Committee]. I care deeply about free and open access to high-quality information, and view projects like Wikipedia as critical infrastructure.

Not from Molly's website:

Molly has intelligent takes on issues of concern to Code4Lib. For example, here's her take on Controlled Digital Lending: [https://www.citationneeded.news/hachette-v-internet-archive/ Big publishers think libraries are the enemy]. She is likely to enjoy and learn from Code4Lib as we enjoy and learn from her.

She can be reached at [molly@mollywhite.net]

==Anne Washington==

Dr. Washington is a public interest technologist and professor of data policy at the NYU Steinhardt school. Her expertise on public sector information currently addresses the emerging governance needs of data science. She has an undergraduate degree in computer science, an MLIS, and a PhD in information systems. She's worked at the Library of Congress and is the Advisory Boards of the Electronic Privacy Information Center (EPIC) and the Open Government Foundation.

[https://annewashington.com/ web site]

[mailto:anne.washington@nyu.edu email address]

==Nikki Stevens==

Dr. Stevens is a faculty associate at Arizona State, maintainer of the [https://github.com/drnikki/open-demographics Open Demographics] project, and past postdoctoral researcher at MIT, in the [https://dataplusfeminism.mit.edu/ Data + Feminism Lab]. Formerly a software engineer, she studies how software engineering is situated in systems of power -- for instance, the ways that relational database architecture dovetails with carceral logics. She says "if you invite me for a talk (hint hint), I would give talks titled:

* “Abolitionist Data Practices: Applying political goals to data structures”
* “Is my database racist? How white supremacy structures our databases”
* “The history of data modeling” (this one is more exciting than it sounds, I swear!)
* “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”

[https://nikkistevens.com/ personal web site]

[mailto:nikki.stevens@asu.edu email]

==Cat Hicks==

Dr. Hicks is a psychologist studying developer thriving. Her social science research includes learning cultures, code review anxiety, and the psychological affordances of organizations. She says "I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity." I think we would be interested in her research, and she would also be interested in code4lib's overlap with and differences from industry tech culture.

[https://www.drcathicks.com/ web site]

[https://mastodon.social/@grimalkina mastodon]

[https://www.changetechnically.fyi/ podcast]

==Meredith Martin==

As Director of the Center for Digital Humanities at Princeton, she has pioneered interdisciplinary initiatives, fostering collaboration across departments and institutions worldwide. She co-chairs the Artificial Intelligence + Digital Humanities special interest group for the Association for Computers and the Humanities and is an editor of the Journal of Cultural Analytics. As Director of the Center for Digital Humanities at Princeton University, Professor Martin is a leading expert on the intersection of technology and the humanities. Her innovative work, including the Princeton Prosody Archive and forthcoming Poetry’s Data, explores how technologies like natural language processing and machine learning can transform humanities research. Professor Martin would provide a thought-provoking keynote, sparking meaningful discussions about the evolving role of technology in academia and beyond.

Link to CDH /[https://cdh.princeton.edu/people/meredith-martin/ ] that illustrates why Jane would be a good keynote speaker.

[mailto:mm4@princeton.edu Meredith Martin]

[https://www.dariah.eu/2024/10/17/meredith-martin-cdh-faculty-director-discusses-the-evolution-of-the-humanities-engagement-with-data-at-the-dariah-annual-event/ DARIAH EU]

==Jane Doe (example)==

Jane works at ________, doing _______.

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

[mailto:jane@nowhere.foo janes_email_address]

2023 Keynote Speakers Nominations

2022-11-07T22:05:39Z

Kayiwa: Nominate Dr. Grady

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

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

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

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

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

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

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

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

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

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

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

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

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

</pre>

__TOC__

== Dr. Siobahn Day Grady ==

Dr. Grady serves as a beacon for (especially) women of color in STEM. She is a computer and information scientist and the first woman to graduate with a computer science Ph.D. from the College of Engineering at N.C. A&T State University, was chosen as a STEM Ambassador by the If/Then Initiative, which seeks to bring more women and minorities into hard sciences, technology, engineering and mathematics. As an Assistant Professor at the only ALA-Accredited HBCU Library School Dr. Grady continues to create a vision for minority girls' and women's futures. She realizes that vision by providing educational opportunities through community organizations, philanthropic efforts, college courses and research grants and publications.

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

[mailto:sday@nccu.edu Siobahn Grady]

==Jane Doe (example)==

Jane works at ________, doing _______.

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

[mailto:jane@nowhere.foo janes_email_address]

Code4Lib 2022 Conference Committees

2022-02-09T00:39:08Z

Kayiwa: Amanda McCormick Update

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa at princeton dot edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org) - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Dave Erlandson - (de12@rice.edu) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Jenn Bielewski - (jennifer.bielewski@lyrasis.org) - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Ken Irwin (irwinkr at miamioh.edu) - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Anne Slaughter (anne dot slaughter at railslibraries dot info) - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod at uchicago dot edu) - Primary Contact AKA Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* Megan Kudzia - (kudzia at msu dot edu ) - Volunteer
* Sharon Clapp - (sclapp@ccsu.edu) Volunteer
* Your Name Here - Volunteer

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

[[2022 Program Documents|2022 Program Documents]]

* Daricus Larry - (dlarry@arizona.edu) - Primary Contact AKA Chair
* Matt Sherman - (matt.r.sherman@gmail.com) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Heather Greer Klein - (heather@samvera.org) - Documentarian
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - Volunteer
* Jenn Bielewski - (Jennifer.Bielewski@lyrasis.org) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Jessica Benner - (jbenner@andrew.cmu.edu) - Primary Contact AKA Chair
* Yongming Wang - (wangyo@tcnj.edu) - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Tiffany Henry - Volunteer
* Esther Jackson - Volunteer
* Claire Payne - Volunteer
* Ashley Evans Bandy - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Guita Lamsechi - (guita.lamsechi@utoronto.ca) - Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Volunteer
* Jackie Gosselar - (gosselar@berkeley.edu) - Volunteer
* Sharon Clapp - (sclapp@ccsu.edu) 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Omar Brown - (omarbrow@buffalo.edu) - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:ThomasGuignard|Thomas Guignard]] (tom@timtom.ca) - 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Ashlea Green - (greenam7@appstate.edu) - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Christine McClure (camcclure@gmail.com) - Volunteer
* Kelly Stathis (kelly.stathis@engagedri.ca) - 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.

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Rebekah Burke - Volunteer
* [[User:ThomasGuignard|Thomas Guignard]] (tom@timtom.ca) - Volunteer

[[Category:Code4Lib2022]]

2022 Keynote Speakers Nominations

2021-11-05T16:27:21Z

Kayiwa: Add Julia Evans.

Code4Lib 2022 will take place May 23 and May 26, 2022 in Buffalo, NY.

''We encourage nominations for speakers located in the Great Lakes region, but welcome nominations from any location.''

'''We will be accepting nominations from October 28, 2021 until November 18, 2021.'''

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

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Margaret Heller at mheller1@luc.edu [mailto:mheller1@luc.edu mheller1@luc.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

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

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

</pre>

__TOC__

==Jane Doe (example)==

Jane works at ________, doing _______.

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

[mailto:jane@nowhere.foo janes_email_address]

==Lauren Chambers==
Lauren is a Ph.D. student at the Berkeley iSchool, focused on data and society issues. Previously she was staff technologist at the ACLU of Massachusetts, where (among other things) she fought against government use of facial recognition technology and co-organized a workshop where drag queens taught anti-surveillance makeup techniques in a public library. Before that, she was an astrophysicist.

[https://laurenmarietta.github.io/contact.html web site contact page]

==Serena Oduro==
Serena has worked on anti-racist tech equity and policy issues at [https://datasociety.net/ Data & Society] and [https://greenlining.org/ Greenlining]. [https://datasociety.net/people/serena-oduro/ "Serena received a BA in History from Seattle University where she also minored in Philosophy, Business, Global African Studies, and Mandarin"], and all of that background shows up in her talks. She's worked and studied in England, Poland, and Ghana.

(I have her email address from non-public sources, so I'm not going to put it on the wiki, but I can reach out to her. --andromeda)

== Julia Evans ==

Julia Evans is a Montreal-based software developer at Stripe. They have an effective way of teaching or explaining technology using cartoons. This fun way of talking and thinking about technology will be worth listening to.

[https://jvns.ca/teach-tech-with-cartoons/ teach technology]

[https://jvns.ca/about/ Julia's Contact Information]

Code4Lib 2022 Conference Committees

2021-10-07T19:59:12Z

Kayiwa:

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa at princeton dot edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org) - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Dave Erlandson - (de12@rice.edu) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Ken Irwin (irwinkr at miamioh.edu) - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod at uchicago dot edu) - Primary Contact AKA Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* Megan Kudzia - (kudzia at msu dot edu ) - 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.

[[2022 Program Documents|2022 Program Documents]]

* Daricus Larry - (dlarry@arizona.edu) - Primary Contact AKA Chair
* Matt Sherman - (matt.r.sherman@gmail.com) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Heather Greer Klein - (heather@samvera.org) - Documentarian
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - Volunteer
* Your Name Here - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Yongming Wang - (wangyo@tcnj.edu) - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Omar Brown - (omarbrow@buffalo.edu) - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-24T14:56:24Z

Kayiwa:

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa at princeton dot edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org0 - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod at uchicago dot edu) - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry - (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Matt Sherman - (matt.r.sherman@gmail.com) - Volunteer
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-24T14:55:48Z

Kayiwa:

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa@princeton.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org0 - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod at uchicago dot edu) - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry - (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Matt Sherman - (matt.r.sherman@gmail.com) - Volunteer
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-24T14:55:14Z

Kayiwa: Margaret volunteers!

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa@princeton.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org0 - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod@uchicago.edu) - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry - (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Matt Sherman - (matt.r.sherman@gmail.com) - Volunteer
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-24T14:47:55Z

Kayiwa: tod volunteers

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa@princeton.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org0 - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Your Name Here - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa@princeton.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod@uchicago.edu) - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry - (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Matt Sherman - (matt.r.sherman@gmail.com) - Volunteer
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - 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.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-09T18:45:00Z

Kayiwa:

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Karlen Chase (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian, Secondary Contact, Tertiary Contact
* Francis Kayiwa (kayiwa@princeton.edu) - Tertiary Contact
* Molly Maloney (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt (rmorcutt@buffalo.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell (cmklotzb@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Documentarian/Planning Committee Contact
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes virtual social activities.

2022 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-09T18:44:17Z

Kayiwa: documents

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Karlen Chase (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian, Tertiary Contact
* Francis Kayiwa (kayiwa@princeton.edu) - Tertiary Contact
* Molly Maloney (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt (rmorcutt@buffalo.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell (cmklotzb@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Documentarian/Planning Committee Contact
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes virtual social activities.

2022 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2022 Conference Committees

2021-09-09T18:42:01Z

Kayiwa: LPC

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 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 ==

* Your Name Here -conferences:

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

* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Karlen Chase (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Tertiary Contact
* Francis Kayiwa (kayiwa@princeton.edu) - Tertiary Contact
* Molly Maloney (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt (rmorcutt@buffalo.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell (cmklotzb@buffalo.edu) - Tertiary Contact

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

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

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

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Documentarian/Planning Committee Contact
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes virtual social activities.

2022 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Category:Code4Lib2013

2018-10-30T15:57:31Z

Kayiwa: Finally found the bitbucket repo with the proposal.

{{Conference
|URL=http://code4lib.org/conference/2013
|Start Date= February 11, 2013
|End Date= February 14, 2013
|Location=Chicago, IL
|Logo=File:Metadata.jpg
}}

Wiki pages related to the Code4Lib 2013 meeting to be held in Chicago, IL. See the [https://bitbucket.org/kayiwa/code4lib2013/src/default/ proposal from University of Illinois Chicago].

*[http://code4lib.org/conference/2013/schedule 2013 Schedule]
*[[2013 Lightning Talks Signup]]
*[https://docs.google.com/document/d/1TahfqabnchZLD1opq6ILs8XCYdXkgJDsj8-WyVLNzI4/edit Breakout Session Signups] | [[2013_breakout_sessions_reports|2013 Breakout Sessions Reports]]
*[[2013_committees_sign-up_page|Volunteer to help plan 2013 conference]]
*[[2013_During_the_Conference_Volunteers|During the conference volunteer signup]]
*[[2013 Invited Speakers Nominations]] -- nominations close Aug. 31, 2012.
*[[2013 preconference proposals|2013 preconference sessions]] - try to sign up by Jan 15th
*[[2013 talks proposals]] - due Friday, Nov 9
*[[2013 t-shirt design proposals]] - due Monday, Dec. 31
**[[media:Metadata.jpg|winning design]]

*[[2013_social_activities|Social Activities for 2013 Conference]]
*[[2013_travel|Travel Advice and Getting To and From the 2013 Conference]]
*[[2013_room_ride_share|2013 Conference Room and Ride Share]]
*[[2013_Guide_To_Wireless| Connecting to the UIC's Wifi]]
*[[2013 Twitter List| 2013 Twitter Attendee List]]

* Conference hashtag: #c4l13 -- [https://docs.google.com/spreadsheet/ccc?key=0AsyivMoYhk87dFljMUZURWZMYzNzT2lwcEduUUJ6d1E#gid=113 Archive of tweets] | [http://www.flickr.com/search/?q=c4l13 Flickr photos]

2019 Keynote Speakers Nominations

2018-10-01T23:26:35Z

Kayiwa:

Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.

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

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the San José area.''

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__

==Jane Doe (example)==

Jane works at ________, doing _______.

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

==Tara Robertson ==

Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year.

More on [https://tararobertson.ca Tara].

[[Category:Code4Lib2019]]

[[Category:Code4Lib2019]]

2019 Keynote Speakers Nominations

2018-10-01T23:26:11Z

Kayiwa:

Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.

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

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the San José area.''

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__

==Jane Doe (example)==

Jane works at ________, doing _______.

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

==Tara Robertson ==

Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year.

More on [https://tararobertson.ca Tara] can be found at the link below.

[[Category:Code4Lib2019]]

[[Category:Code4Lib2019]]

2019 Keynote Speakers Nominations

2018-10-01T23:22:52Z

Kayiwa: Adding Tara Robertson.

Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.

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

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the San José area.''

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__

==Jane Doe (example)==

Jane works at ________, doing _______.

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

==Tara Robertson ==

Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year.

More on Tara [https://tararobertson.ca] can be found at the link below.

[[Category:Code4Lib2019]]

[[Category:Code4Lib2019]]

2017 Keynote Speakers Nominations

2016-10-12T13:45:46Z

Kayiwa: /* Christina Harlow */

Nominations for invited speakers/keynotes for Code4Lib 2017 in Los Angeles. 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__

==Jane Doe (example)==
Jane works at ________, doing _______.

Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.

== Maciej Celgowski ==

Maciej Celgowski is the founder of the bookmarking site [http://pinboard.in Pinboard], [https://blog.pinboard.in/2010/12/merry_christmas_librarians/ a friend to librarians], a writer of [http://idlewords.com/ popular internet essays], and an entertaining speaker on topics including data, privacy, webpage bloat, and online fandom. He also operates [https://twitter.com/Pinboard a snarky Twitter account]. His most recent talk was [http://idlewords.com/talks/deep_fried_data.htm Deep Fried Data], given at the Library of Congress Collections as Data event in September of 2016. Other talks of interest include [http://idlewords.com/talks/internet_with_a_human_face.htm The Internet With a Human Face] and [http://idlewords.com/talks/fan_is_a_tool_using_animal.htm Fan is a Tool Using Animal].

Talks archive: http://idlewords.com/talks/ (contact info is at the bottom of the page)

== Dragan Espenscheid ==

Dragan Espenschied (*1975 in Germany) is a media artist, home computer folk musician and digital culture researcher and conservator living in New York City. Starting out as a net activist in the late 1990’s, he created several online interventions concerned with digital power structures and live network traffic analysis/manipulation together with Alvar Freude.
In his artistic career, Espenschied focuses on the historization of Digital Culture from the perspective of computer users rather than hackers, developers or “inventors”. Together with net art pioneer Olia Lialina he has been creating a significant body of work concerned with how to represent and write a culture-centric history of the networked age. Since 2011, they together have been [http://blog.geocities.institute/ restoring and culturally analyzing 1 TB of GeoCities data], supported by the Swiss National Science Foundation. Espenschied worked with the transmediale festival’s archive and the Vilem Flusser Archive to conceptually and technically integrate large scale emulation while working as a researcher at the University of Freiburg and the University of Applied Arts in Karlsruhe. Publications include papers on large scale curation of complex digital artifacts, emulation and digital culture, the influential reader Digital Folklore as well as musical releases on Aphex Twin’s label Rephlex and several underground/net labels, performing and lecturing in between raves and museums in Europe and the United States. Since April 2014, he is leading the Digital Conservation Program at [https://rhizome.org/ Rhizome].

[http://1x-upon.com/~despens/about/dragan/ http://1x-upon.com/~despens/about/dragan/]

== 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). Ford's 30,000-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]. Paul 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].

== Kelsey Gilmore-Innis ==

Kelsey Gilmore-Innis is the Chief Technology Officer at [http://www.sexualhealthinnovations.org/ Sexual Health Innovations], creating technology that advances sexual health and wellbeing in the United States. SHI is currently building [http://www.projectcallisto.org/ Project Callisto] to provide a more empowering, transparent, and confidential reporting experience for college sexual assault survivors. Kelsey co-founded the Lambda Ladies group for women in functional programming and speaks regularly around the world on technical topics. As part of the Anti-Eviction Mapping Project, she led the development and deployment of the searchable Anti-Eviction Pledge site. Outside of SHI, Kelsey pursues the study of baseball, R&B, presidential trivia and other all-American pursuits.

[https://twitter.com/_K_E_L_S_E_Y https://twitter.com/_K_E_L_S_E_Y]

==Christina Harlow==
Christina is not a consortium of people (I know, I've thought that also) She is a brilliant technologist who works at Cornell University beating data into submission. When she isn't doing that (here's why you've thought her twitter account is a consortium) she is talking about the aforementioned data to likeminded people all while managing to run brilliant conferences. Her ability to describe data munging to "non-natives" is something the entire code4lib community should experience, not just the few who've managed to sit in on her workshops, follow her on Twitter etc., Her generosity has likely impacted many in the code4lib community directly or indirectly. It would also be a chance for her to expand on her Missy Elliot themed talk in Philadelphia.

[http://christinaharlow.com/ http://christinaharlow.com/]

Twitter: [https://twitter.com/cm_harlow @cm_harlow]

== Wendy Hsu ==

Wendy Hsu is a researcher, strategist, and educator who engages with hybrid research and organizing agendas for equality in arts, technology, and civic participation. A former ACLS Public Fellow, Hsu currently works as the digital strategist of the City of Los Angeles Department of Cultural Affairs, providing research and strategy to redesign the department’s data and knowledge architecture. Hsu is also the founder of Lab at DCA, a city staff innovation incubator.

Hsu has published on digital ethnography, sound-based pedagogy, public humanities, open access publishing, Asian American indie rock, Yoko Ono, Taqwacore, and Bollywood. Their academic research on street sound cultures in postcolonial Taiwan focuses on the urban underclass experience of mobility and low-resource technology. Their civic sound data project [http://lalistens.org/ LA Listens] explores the sensory, social, and ecological aspects of Los Angeles streets by providing a creative and engagement platform for community-oriented artists, planners, and organizers. Most recently, Hsu led the maker collective Movable Parts through [http://movableparts.org/projects/karaoke-rickshaw/ Movable Karaoke], a Metro-funded project that evokes and explores the collective mobility experience in LA.

[http://beingwendyhsu.info/ http://beingwendyhsu.info/]

== Bergis Jules ==

Bergis is the University and Political Papers Archivist at University of California, Riverside, and is the Community Lead for [http://www.docnow.io/ Documenting the Now], which focuses on ethically collecting and preserving social media content. Background reading - [https://medium.com/on-archivy/documenting-the-now-ferguson-in-the-archives-adcdbe1d5788?section=%5Bobject%20Object%5D#.nvhvvygy7 Documenting the Now: #Ferguson in the Archives]

[https://medium.com/@BergisJules Medium]

[https://www.youtube.com/watch?v=nXE1hruwg7E Bergis in the Ethics of Social Media Collection and Use panel at DocNow]

Twitter: [https://twitter.com/BergisJules @BergisJules]

== Sarah Mei ==

Sarah is a Ruby and JavaScript developer based in San Francisco. She founded [http://railsbridge.org/ RailsBridge ] and [http://bridgefoundry.org/ Bridge Foundry ]. She is the director of Ruby Central, the non-profit that runs the two largest Ruby conferences in the world.

She's particularly interested in Object Oriented design and [https://www.devmynd.com/blog/2015-1-pairing-with-junior-developers/ pair programming], the effects of dev team social dynamics on code, and increasing community involvement in open source.

[http://confreaks.com/presenters/150-sarah-mei Video of some past talks ]

[http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/ Dangers of shiny technology ]

[http://twitter.com/sarahmei Twitter @sarahmei]

== David S. H. Rosenthal ==
Dr. David Rosenthal started the LOCKSS Program, which is aimed at long-term preservation of web published materials.
[https://www.lockss.org/contact-us/dshr/ https://www.lockss.org/contact-us/dshr/]
[http://blog.dshr.org/ http://blog.dshr.org/]

== Sonali Sridhar ==

Sonali Sridhar is cofounder of the [http://www.recurse.com/ Recurse Center] (formerly Hacker School.) Prior to starting the Recurse Center in 2011, she worked as an Interaction Designer at R/GA, and has now taken on the challenge of designing experiences at the Recurse Center, as she aims to create a Bauhaus for programmers. She lives in Brooklyn, New York, and is a founding member of QUILTBAG++, a New York City-based queer and trans tech group committed to social justice. She is also part of the 2015 Creative Ecology Advisory Board at the The Banff Centre's Peter Lougheed Leadership Institute.

[https://twitter.com/jollysonali https://twitter.com/jollysonali]

== Whitni Watkins ==

Whitni is a Web Systems Engineer for Analog Devices, Inc. where she manages multiple systems for their Technical Marketing and Information Services group. She is an active code4lib community member. With her experiences from academic institutions to a semiconductor company, she would bring in various angles of working in the library and technology field.

LinkedIn: [https://www.linkedin.com/in/whitniwatkins https://www.linkedin.com/in/whitniwatkins]

Twitter: [https://twitter.com/_whitni @_whitni]

== Greg Wilson ==

[http://third-bit.com/about.html Greg Wilson] is the co-founder of [http://software-carpentry.org/about/ Software Carpentry], a volunteer organization that teaches basic computing skills to researchers in a wide range of disciplines. Greg has worked for 30 years in both industry and academia, and is the author or editor of several books on computing and two for children.

Twitter: [https://twitter.com/gvwilson @gvwilson]

== Gene Luen Yang ==
Comic artist and author, Gene Yang has greatly broadened diversity representation in comics with successful titles such as '''American Born Chinese''', '''Boxers and Saints''', and '''The Shadow Hero'''. In 2016, the Library of Congress named him as an Ambassador for Young People’s Literature. In this capacity, Yang has pushed a mission of 'Reading Without Walls' to encourage literacies of all types. Additionally, he has recently started a graphic novel series, '''Secret Coders''' with artist Mike Holmes. This series aims to introduce kids to actual magic they can perform at home: computer programming. As several kids try to uncover the mysteries of their school, they face puzzles and challenges that teach readers about programming.

[http://geneyang.com/ http://geneyang.com/]

[http://geneyang.com/secret-coders http://geneyang.com/secret-coders]

2017 Keynote Speakers Nominations

2016-10-12T13:45:16Z

Kayiwa:

Nominations for invited speakers/keynotes for Code4Lib 2017 in Los Angeles. 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__

==Jane Doe (example)==
Jane works at ________, doing _______.

Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.

== Maciej Celgowski ==

Maciej Celgowski is the founder of the bookmarking site [http://pinboard.in Pinboard], [https://blog.pinboard.in/2010/12/merry_christmas_librarians/ a friend to librarians], a writer of [http://idlewords.com/ popular internet essays], and an entertaining speaker on topics including data, privacy, webpage bloat, and online fandom. He also operates [https://twitter.com/Pinboard a snarky Twitter account]. His most recent talk was [http://idlewords.com/talks/deep_fried_data.htm Deep Fried Data], given at the Library of Congress Collections as Data event in September of 2016. Other talks of interest include [http://idlewords.com/talks/internet_with_a_human_face.htm The Internet With a Human Face] and [http://idlewords.com/talks/fan_is_a_tool_using_animal.htm Fan is a Tool Using Animal].

Talks archive: http://idlewords.com/talks/ (contact info is at the bottom of the page)

== Dragan Espenscheid ==

Dragan Espenschied (*1975 in Germany) is a media artist, home computer folk musician and digital culture researcher and conservator living in New York City. Starting out as a net activist in the late 1990’s, he created several online interventions concerned with digital power structures and live network traffic analysis/manipulation together with Alvar Freude.
In his artistic career, Espenschied focuses on the historization of Digital Culture from the perspective of computer users rather than hackers, developers or “inventors”. Together with net art pioneer Olia Lialina he has been creating a significant body of work concerned with how to represent and write a culture-centric history of the networked age. Since 2011, they together have been [http://blog.geocities.institute/ restoring and culturally analyzing 1 TB of GeoCities data], supported by the Swiss National Science Foundation. Espenschied worked with the transmediale festival’s archive and the Vilem Flusser Archive to conceptually and technically integrate large scale emulation while working as a researcher at the University of Freiburg and the University of Applied Arts in Karlsruhe. Publications include papers on large scale curation of complex digital artifacts, emulation and digital culture, the influential reader Digital Folklore as well as musical releases on Aphex Twin’s label Rephlex and several underground/net labels, performing and lecturing in between raves and museums in Europe and the United States. Since April 2014, he is leading the Digital Conservation Program at [https://rhizome.org/ Rhizome].

[http://1x-upon.com/~despens/about/dragan/ http://1x-upon.com/~despens/about/dragan/]

== 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). Ford's 30,000-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]. Paul 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].

== Kelsey Gilmore-Innis ==

Kelsey Gilmore-Innis is the Chief Technology Officer at [http://www.sexualhealthinnovations.org/ Sexual Health Innovations], creating technology that advances sexual health and wellbeing in the United States. SHI is currently building [http://www.projectcallisto.org/ Project Callisto] to provide a more empowering, transparent, and confidential reporting experience for college sexual assault survivors. Kelsey co-founded the Lambda Ladies group for women in functional programming and speaks regularly around the world on technical topics. As part of the Anti-Eviction Mapping Project, she led the development and deployment of the searchable Anti-Eviction Pledge site. Outside of SHI, Kelsey pursues the study of baseball, R&B, presidential trivia and other all-American pursuits.

[https://twitter.com/_K_E_L_S_E_Y https://twitter.com/_K_E_L_S_E_Y]

==Christina Harlow==
Christina is not a consortium of people (I know, I've thought that also) She is a brilliant technologist who works at Cornell University beating data into submission. When she isn't doing that (here's why you've thought her twitter account is a consortium) she is talking about the aforementioned data to likeminded people all while managing to run brilliant conferences. Her ability to describe data munging to "non-natives" is something the entire code4lib community should experience, not just the few who've managed to sit in on her workshops, follow her on Twitter etc., Her generosity has likely impacted many in the code4lib community directly or indirectly. It would also be a chance for her to expand on her Missy Elliot themed talk in Philadelphia.

[http://christinaharlow.com/ http://christinaharlow.com/]
Twitter: [https://twitter.com/cm_harlow @cm_harlow]

== Wendy Hsu ==

Wendy Hsu is a researcher, strategist, and educator who engages with hybrid research and organizing agendas for equality in arts, technology, and civic participation. A former ACLS Public Fellow, Hsu currently works as the digital strategist of the City of Los Angeles Department of Cultural Affairs, providing research and strategy to redesign the department’s data and knowledge architecture. Hsu is also the founder of Lab at DCA, a city staff innovation incubator.

Hsu has published on digital ethnography, sound-based pedagogy, public humanities, open access publishing, Asian American indie rock, Yoko Ono, Taqwacore, and Bollywood. Their academic research on street sound cultures in postcolonial Taiwan focuses on the urban underclass experience of mobility and low-resource technology. Their civic sound data project [http://lalistens.org/ LA Listens] explores the sensory, social, and ecological aspects of Los Angeles streets by providing a creative and engagement platform for community-oriented artists, planners, and organizers. Most recently, Hsu led the maker collective Movable Parts through [http://movableparts.org/projects/karaoke-rickshaw/ Movable Karaoke], a Metro-funded project that evokes and explores the collective mobility experience in LA.

[http://beingwendyhsu.info/ http://beingwendyhsu.info/]

== Bergis Jules ==

Bergis is the University and Political Papers Archivist at University of California, Riverside, and is the Community Lead for [http://www.docnow.io/ Documenting the Now], which focuses on ethically collecting and preserving social media content. Background reading - [https://medium.com/on-archivy/documenting-the-now-ferguson-in-the-archives-adcdbe1d5788?section=%5Bobject%20Object%5D#.nvhvvygy7 Documenting the Now: #Ferguson in the Archives]

[https://medium.com/@BergisJules Medium]

[https://www.youtube.com/watch?v=nXE1hruwg7E Bergis in the Ethics of Social Media Collection and Use panel at DocNow]

Twitter: [https://twitter.com/BergisJules @BergisJules]

== Sarah Mei ==

Sarah is a Ruby and JavaScript developer based in San Francisco. She founded [http://railsbridge.org/ RailsBridge ] and [http://bridgefoundry.org/ Bridge Foundry ]. She is the director of Ruby Central, the non-profit that runs the two largest Ruby conferences in the world.

She's particularly interested in Object Oriented design and [https://www.devmynd.com/blog/2015-1-pairing-with-junior-developers/ pair programming], the effects of dev team social dynamics on code, and increasing community involvement in open source.

[http://confreaks.com/presenters/150-sarah-mei Video of some past talks ]

[http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/ Dangers of shiny technology ]

[http://twitter.com/sarahmei Twitter @sarahmei]

== David S. H. Rosenthal ==
Dr. David Rosenthal started the LOCKSS Program, which is aimed at long-term preservation of web published materials.
[https://www.lockss.org/contact-us/dshr/ https://www.lockss.org/contact-us/dshr/]
[http://blog.dshr.org/ http://blog.dshr.org/]

== Sonali Sridhar ==

Sonali Sridhar is cofounder of the [http://www.recurse.com/ Recurse Center] (formerly Hacker School.) Prior to starting the Recurse Center in 2011, she worked as an Interaction Designer at R/GA, and has now taken on the challenge of designing experiences at the Recurse Center, as she aims to create a Bauhaus for programmers. She lives in Brooklyn, New York, and is a founding member of QUILTBAG++, a New York City-based queer and trans tech group committed to social justice. She is also part of the 2015 Creative Ecology Advisory Board at the The Banff Centre's Peter Lougheed Leadership Institute.

[https://twitter.com/jollysonali https://twitter.com/jollysonali]

== Whitni Watkins ==

Whitni is a Web Systems Engineer for Analog Devices, Inc. where she manages multiple systems for their Technical Marketing and Information Services group. She is an active code4lib community member. With her experiences from academic institutions to a semiconductor company, she would bring in various angles of working in the library and technology field.

LinkedIn: [https://www.linkedin.com/in/whitniwatkins https://www.linkedin.com/in/whitniwatkins]

Twitter: [https://twitter.com/_whitni @_whitni]

== Greg Wilson ==

[http://third-bit.com/about.html Greg Wilson] is the co-founder of [http://software-carpentry.org/about/ Software Carpentry], a volunteer organization that teaches basic computing skills to researchers in a wide range of disciplines. Greg has worked for 30 years in both industry and academia, and is the author or editor of several books on computing and two for children.

Twitter: [https://twitter.com/gvwilson @gvwilson]

== Gene Luen Yang ==
Comic artist and author, Gene Yang has greatly broadened diversity representation in comics with successful titles such as '''American Born Chinese''', '''Boxers and Saints''', and '''The Shadow Hero'''. In 2016, the Library of Congress named him as an Ambassador for Young People’s Literature. In this capacity, Yang has pushed a mission of 'Reading Without Walls' to encourage literacies of all types. Additionally, he has recently started a graphic novel series, '''Secret Coders''' with artist Mike Holmes. This series aims to introduce kids to actual magic they can perform at home: computer programming. As several kids try to uncover the mysteries of their school, they face puzzles and challenges that teach readers about programming.

[http://geneyang.com/ http://geneyang.com/]

[http://geneyang.com/secret-coders http://geneyang.com/secret-coders]

2017 Keynote Speakers Nominations

2016-10-12T13:44:39Z

Kayiwa: Added Harlow and Twitter Link for Bergis Jules

Nominations for invited speakers/keynotes for Code4Lib 2017 in Los Angeles. 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__

==Jane Doe (example)==
Jane works at ________, doing _______.

Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.

== Maciej Celgowski ==

Maciej Celgowski is the founder of the bookmarking site [http://pinboard.in Pinboard], [https://blog.pinboard.in/2010/12/merry_christmas_librarians/ a friend to librarians], a writer of [http://idlewords.com/ popular internet essays], and an entertaining speaker on topics including data, privacy, webpage bloat, and online fandom. He also operates [https://twitter.com/Pinboard a snarky Twitter account]. His most recent talk was [http://idlewords.com/talks/deep_fried_data.htm Deep Fried Data], given at the Library of Congress Collections as Data event in September of 2016. Other talks of interest include [http://idlewords.com/talks/internet_with_a_human_face.htm The Internet With a Human Face] and [http://idlewords.com/talks/fan_is_a_tool_using_animal.htm Fan is a Tool Using Animal].

Talks archive: http://idlewords.com/talks/ (contact info is at the bottom of the page)

== Dragan Espenscheid ==

Dragan Espenschied (*1975 in Germany) is a media artist, home computer folk musician and digital culture researcher and conservator living in New York City. Starting out as a net activist in the late 1990’s, he created several online interventions concerned with digital power structures and live network traffic analysis/manipulation together with Alvar Freude.
In his artistic career, Espenschied focuses on the historization of Digital Culture from the perspective of computer users rather than hackers, developers or “inventors”. Together with net art pioneer Olia Lialina he has been creating a significant body of work concerned with how to represent and write a culture-centric history of the networked age. Since 2011, they together have been [http://blog.geocities.institute/ restoring and culturally analyzing 1 TB of GeoCities data], supported by the Swiss National Science Foundation. Espenschied worked with the transmediale festival’s archive and the Vilem Flusser Archive to conceptually and technically integrate large scale emulation while working as a researcher at the University of Freiburg and the University of Applied Arts in Karlsruhe. Publications include papers on large scale curation of complex digital artifacts, emulation and digital culture, the influential reader Digital Folklore as well as musical releases on Aphex Twin’s label Rephlex and several underground/net labels, performing and lecturing in between raves and museums in Europe and the United States. Since April 2014, he is leading the Digital Conservation Program at [https://rhizome.org/ Rhizome].

[http://1x-upon.com/~despens/about/dragan/ http://1x-upon.com/~despens/about/dragan/]

== 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). Ford's 30,000-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]. Paul 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].

== Kelsey Gilmore-Innis ==

Kelsey Gilmore-Innis is the Chief Technology Officer at [http://www.sexualhealthinnovations.org/ Sexual Health Innovations], creating technology that advances sexual health and wellbeing in the United States. SHI is currently building [http://www.projectcallisto.org/ Project Callisto] to provide a more empowering, transparent, and confidential reporting experience for college sexual assault survivors. Kelsey co-founded the Lambda Ladies group for women in functional programming and speaks regularly around the world on technical topics. As part of the Anti-Eviction Mapping Project, she led the development and deployment of the searchable Anti-Eviction Pledge site. Outside of SHI, Kelsey pursues the study of baseball, R&B, presidential trivia and other all-American pursuits.

[https://twitter.com/_K_E_L_S_E_Y https://twitter.com/_K_E_L_S_E_Y]

==Christina Harlow (example)==
Christina is not a consortium of people (I know, I've thought that also) She is a brilliant technologist who works at Cornell University beating data into submission. When she isn't doing that (here's why you've thought her twitter account is a consortium) she is talking about the aforementioned data to likeminded people all while managing to run brilliant conferences. Her ability to describe data munging to "non-natives" is something the entire code4lib community should experience, not just the few who've managed to sit in on her workshops, follow her on Twitter etc., Her generosity has likely impacted many in the code4lib community directly or indirectly. It would also be a chance for her to expand on her Missy Elliot themed talk in Philadelphia.

[http://christinaharlow.com/ http://christinaharlow.com/]
Twitter: [https://twitter.com/cm_harlow @cm_harlow]

== Wendy Hsu ==

Wendy Hsu is a researcher, strategist, and educator who engages with hybrid research and organizing agendas for equality in arts, technology, and civic participation. A former ACLS Public Fellow, Hsu currently works as the digital strategist of the City of Los Angeles Department of Cultural Affairs, providing research and strategy to redesign the department’s data and knowledge architecture. Hsu is also the founder of Lab at DCA, a city staff innovation incubator.

Hsu has published on digital ethnography, sound-based pedagogy, public humanities, open access publishing, Asian American indie rock, Yoko Ono, Taqwacore, and Bollywood. Their academic research on street sound cultures in postcolonial Taiwan focuses on the urban underclass experience of mobility and low-resource technology. Their civic sound data project [http://lalistens.org/ LA Listens] explores the sensory, social, and ecological aspects of Los Angeles streets by providing a creative and engagement platform for community-oriented artists, planners, and organizers. Most recently, Hsu led the maker collective Movable Parts through [http://movableparts.org/projects/karaoke-rickshaw/ Movable Karaoke], a Metro-funded project that evokes and explores the collective mobility experience in LA.

[http://beingwendyhsu.info/ http://beingwendyhsu.info/]

== Bergis Jules ==

Bergis is the University and Political Papers Archivist at University of California, Riverside, and is the Community Lead for [http://www.docnow.io/ Documenting the Now], which focuses on ethically collecting and preserving social media content. Background reading - [https://medium.com/on-archivy/documenting-the-now-ferguson-in-the-archives-adcdbe1d5788?section=%5Bobject%20Object%5D#.nvhvvygy7 Documenting the Now: #Ferguson in the Archives]

[https://medium.com/@BergisJules Medium]

[https://www.youtube.com/watch?v=nXE1hruwg7E Bergis in the Ethics of Social Media Collection and Use panel at DocNow]

Twitter: [https://twitter.com/BergisJules @BergisJules]

== Sarah Mei ==

Sarah is a Ruby and JavaScript developer based in San Francisco. She founded [http://railsbridge.org/ RailsBridge ] and [http://bridgefoundry.org/ Bridge Foundry ]. She is the director of Ruby Central, the non-profit that runs the two largest Ruby conferences in the world.

She's particularly interested in Object Oriented design and [https://www.devmynd.com/blog/2015-1-pairing-with-junior-developers/ pair programming], the effects of dev team social dynamics on code, and increasing community involvement in open source.

[http://confreaks.com/presenters/150-sarah-mei Video of some past talks ]

[http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/ Dangers of shiny technology ]

[http://twitter.com/sarahmei Twitter @sarahmei]

== David S. H. Rosenthal ==
Dr. David Rosenthal started the LOCKSS Program, which is aimed at long-term preservation of web published materials.
[https://www.lockss.org/contact-us/dshr/ https://www.lockss.org/contact-us/dshr/]
[http://blog.dshr.org/ http://blog.dshr.org/]

== Sonali Sridhar ==

Sonali Sridhar is cofounder of the [http://www.recurse.com/ Recurse Center] (formerly Hacker School.) Prior to starting the Recurse Center in 2011, she worked as an Interaction Designer at R/GA, and has now taken on the challenge of designing experiences at the Recurse Center, as she aims to create a Bauhaus for programmers. She lives in Brooklyn, New York, and is a founding member of QUILTBAG++, a New York City-based queer and trans tech group committed to social justice. She is also part of the 2015 Creative Ecology Advisory Board at the The Banff Centre's Peter Lougheed Leadership Institute.

[https://twitter.com/jollysonali https://twitter.com/jollysonali]

== Whitni Watkins ==

Whitni is a Web Systems Engineer for Analog Devices, Inc. where she manages multiple systems for their Technical Marketing and Information Services group. She is an active code4lib community member. With her experiences from academic institutions to a semiconductor company, she would bring in various angles of working in the library and technology field.

LinkedIn: [https://www.linkedin.com/in/whitniwatkins https://www.linkedin.com/in/whitniwatkins]

Twitter: [https://twitter.com/_whitni @_whitni]

== Greg Wilson ==

[http://third-bit.com/about.html Greg Wilson] is the co-founder of [http://software-carpentry.org/about/ Software Carpentry], a volunteer organization that teaches basic computing skills to researchers in a wide range of disciplines. Greg has worked for 30 years in both industry and academia, and is the author or editor of several books on computing and two for children.

Twitter: [https://twitter.com/gvwilson @gvwilson]

== Gene Luen Yang ==
Comic artist and author, Gene Yang has greatly broadened diversity representation in comics with successful titles such as '''American Born Chinese''', '''Boxers and Saints''', and '''The Shadow Hero'''. In 2016, the Library of Congress named him as an Ambassador for Young People’s Literature. In this capacity, Yang has pushed a mission of 'Reading Without Walls' to encourage literacies of all types. Additionally, he has recently started a graphic novel series, '''Secret Coders''' with artist Mike Holmes. This series aims to introduce kids to actual magic they can perform at home: computer programming. As several kids try to uncover the mysteries of their school, they face puzzles and challenges that teach readers about programming.

[http://geneyang.com/ http://geneyang.com/]

[http://geneyang.com/secret-coders http://geneyang.com/secret-coders]

Libraries Sharing Code

2016-03-08T19:24:16Z

Kayiwa: /* Institutions on GitHub */

A number of libraries have organizational repositories in GitHub. These can be very valuable and we attempt to collect them here.

==Institutions on GitHub==
* [https://github.com/aadl Ann Arbor District Library]
* [https://github.com/BCLibCoop BC Libraries Cooperative]
* [https://github.com/BCLIbraries Boston College Libraries]
* [https://github.com/britishlibrary The British Library]
* [https://github.com/Brown-University-Library Brown University Library]
* [https://github.com/cca California College of the Arts]
* [https://github.com/csusm-library CSU San Marcos]
* [https://github.com/clcdpc Central Library Consortium]
* [https://github.com/chattlibrary Chattanooga Public Library] (currently empty)
* [https://github.com/cul Columbia University Libraries]
* [https://github.com/DarienLibrary Darien (CT) Library]
* [https://github.com/duke-libraries Duke University Libraries]
* [https://github.com/gwu-libraries George Washington University Libraries]
* [https://github.com/Georgetown-University-Libraries Georgetown University Libraries]
* [https://github.com/subugoe Göttingen State and University Library]
* [https://github.com/gvsulib Grand Valley State University Libraries]
* [https://github.com/GrinnellCollegeLibraries Grinnell College Libraries]
* [https://github.com/harvard-library Harvard University Library Technology Services]
* [https://github.com/LibraryOfCongress Library of Congress]
* [https://github.com/LibraryofVA Library of Virginia]
* [https://github.com/LincolnUniLTL Lincoln University Library Teaching and Learning] (New Zealand)
* [https://github.com/ndlib University of Notre Dame Hesburgh Libraries] (And [https://github.com/ndlibersa the CORAL stuff])
* [https://github.com/mitlibraries MIT Libraries]
* [https://github.com/MontclairState Montclair State]
* [https://github.com/njstatelibrary New Jersey State Library]
* [https://github.com/nla National Library of Australia]
* [https://github.com/nims-library Scientific Information Office, National Institute for Materials Science (NIMS Library)]
* [https://github.com/NCSU-Libraries NCSU Libraries]
* [https://github.com/nypl The New York Public Library]
* [https://github.com/NYULibraries NYU Libraries]
* [https://github.com/RockefellerArchiveCenter Rockefeller Archive Center]
* [https://github.com/osulibraries Ohio State University Libraries]
* [https://github.com/osulp Oregon State University Libraries & Press]
* [https://github.com/psu-stewardship Penn State Digital Stewardship]
* [https://github.com/pulibrary Princeton University Library]
* [https://github.com/ryersonlibrary Ryerson University Library & Archives]
* [https://github.com/adsabs SAO/NASA Astrophysics Data System]
* [https://github.com/slub Saxon State and University Library Dresden]
* [https://github.com/scds Sherman Centre for Digital Scholarship, McMaster University]
* [https://github.com/sul-dlss Stanford University Digital Library]
* [https://github.com/UBCLIBSYS UBC Library Systems and IT]
* [https://github.com/ualbertalib University of Alberta Libraries]
* [https://github.com/ualibraries The University of Arizona Libraries]
* [https://github.com/ucalgarylib University of Calgary Libraries & Cultural Resources]
* [https://github.com/uc-data-services UC Berkeley Library Data & GIS Services]
* [https://github.com/UCLALibrary UCLA Library]
* [https://github.com/UCSCLibrary UCSC Library]
* [https://github.com/ucsdlib UCSD Library]
* [https://github.com/umd-lib University of Maryland Libraries]
* [https://github.com/UMNLibraries University of Minnesota Libraries]
* [https://github.com/UNC-Libraries University of North Carolina at Chapel Hill Libraries]
* [https://github.com/ui-libraries University of Iowa Libraries]
* [https://github.com/vculibraries Virginia Commonwealth University Libraries]
* [https://github.com/vtul Virginia Polytechnic and State University Libraries]
* [https://github.com/wellcomelibrary Wellcome Library]
* [https://github.com/yalemssa Manuscripts and Archives, Yale University Library]
* [https://github.com/yorkulibraries York University Libraries]

==Institutions with Non-GitHub open repositories==
* University of Florida: SobekCM software [http://sourceforge.net/directory/?q=sobekcm Sourceforge], [http://code.google.com/p/sobekcm/ Google code], [http://ufdc.ufl.edu/software UFDC institutional site]
* [http://eXtensibleCatalog.org eXtensible Catalog] repositories: [http://code.google.com/p/xcmetadataservicestoolkit/ Metadata Services Toolkit], [http://code.google.com/p/xcoaitoolkit/ OAI Toolkit], [http://code.google.com/p/xcncip2toolkit/ NCIP Toolkit] (all these on Google code), [http://drupal.org/project/xc Drupal Toolkit] (on drupal.org)
* [http://git.sitka.bclibraries.ca BC Libraries Cooperative]
* [https://bitbucket.org/uwlib/ UW Libraries]

==Other Library Organizations on GitHub==
* [https://github.com/projectblacklight Project Blacklight]
* [https://github.com/projecthydra Project Hydra]
* [https://github.com/islandora Islandora]
* [https://github.com/artefactual Artefactual], along with projects: [https://github.com/artefactual/atom AtoM], and [https://github.com/artefactual/archivematica Archivematica]
* [https://github.com/duraspace DuraSpace], along with projects: [https://github.com/dspace DSpace], [https://github.com/fcrepo4/ Fedora], and [https://svn.duraspace.org/view/duracloud/ DuraCloud (not yet on GitHub)]
* [https://github.com/hbz/ North Rhine-Westphalian Library Service Center (hbz)] and its service [https://github.com/lobid/ lobid]

* [https://github.com/pkp Public Knowledge Project], along with projects: [https://github.com/pkp/ojs Open Journal Systems], [https://github.com/pkp/ocs Open Conference Systems], and [https://github.com/pkp/omp Open Monograph Press]
* [https://github.com/internetarchive Internet Archive]
* [https://github.com/openlibrary Open Library Team]
* [https://github.com/scholarslab Scholars' Lab]
* [https://github.com/next-l Project Next-L]
* [http://librecat.org/ LibreCat Open Tools for Library and Research Services]
* [https://github.com/swissbib/ swissbib information services for Swiss university libraries and Swiss National library]
* [https://github.com/TEIC Text Encoding Initiative Consortium]

==Individuals on GitHub==
* [https://github.com/jronallo Jason Ronallo] North Carolina State University
* [https://github.com/cazzerson Jason Casden] North Carolina State University
* [https://github.com/jbfink John Fink] McMaster University
* [https://github.com/rgilmour70 Ron Gilmour] Ithaca College
* [https://github.com/mreidsma Matthew Reidsma] Grand Valley State University
* [https://github.com/mjsuhonos MJ Suhonos] Ryerson University Library & Archives
* [https://github.com/mjordan Mark Jordan] Simon Fraser University Library
* [https://github.com/jneubert Joachim Neubert] ZBW - Leibniz Information Centre for Economics
* [https://github.com/phette23 Eric Phetteplace] - California College of the Arts
* [https://github.com/barmintor Ben Armintor] Fedora 3, Blacklight, Hydra Projects
* [https://github.com/techbrarian Jason Bengtson] Houston Academy of Medicine/Texas Medical Center

Libraries Sharing Code

2016-02-26T21:10:13Z

Kayiwa: /* Institutions with Non-GitHub open repositories */

A number of libraries have organizational repositories in GitHub. These can be very valuable and we attempt to collect them here.

==Institutions on GitHub==
* [https://github.com/aadl Ann Arbor District Library]
* [https://github.com/BCLibCoop BC Libraries Cooperative]
* [https://github.com/BCLIbraries Boston College Libraries]
* [https://github.com/britishlibrary The British Library]
* [https://github.com/Brown-University-Library Brown University Library]
* [https://github.com/cca California College of the Arts]
* [https://github.com/csusm-library CSU San Marcos]
* [https://github.com/clcdpc Central Library Consortium]
* [https://github.com/chattlibrary Chattanooga Public Library] (currently empty)
* [https://github.com/cul Columbia University Libraries]
* [https://github.com/DarienLibrary Darien (CT) Library]
* [https://github.com/duke-libraries Duke University Libraries]
* [https://github.com/gwu-libraries George Washington University Libraries]
* [https://github.com/Georgetown-University-Libraries Georgetown University Libraries]
* [https://github.com/subugoe Göttingen State and University Library]
* [https://github.com/gvsulib Grand Valley State University Libraries]
* [https://github.com/GrinnellCollegeLibraries Grinnell College Libraries]
* [https://github.com/harvard-library Harvard University Library Technology Services]
* [https://github.com/LibraryOfCongress Library of Congress]
* [https://github.com/LibraryofVA Library of Virginia]
* [https://github.com/LincolnUniLTL Lincoln University Library Teaching and Learning] (New Zealand)
* [https://github.com/ndlib University of Notre Dame Hesburgh Libraries] (And [https://github.com/ndlibersa the CORAL stuff])
* [https://github.com/mitlibraries MIT Libraries]
* [https://github.com/MontclairState Montclair State]
* [https://github.com/njstatelibrary New Jersey State Library]
* [https://github.com/nla National Library of Australia]
* [https://github.com/nims-library Scientific Information Office, National Institute for Materials Science (NIMS Library)]
* [https://github.com/NCSU-Libraries NCSU Libraries]
* [https://github.com/nypl The New York Public Library]
* [https://github.com/NYULibraries NYU Libraries]
* [https://github.com/RockefellerArchiveCenter Rockefeller Archive Center]
* [https://github.com/osulibraries Ohio State University Libraries]
* [https://github.com/osulp Oregon State University Libraries & Press]
* [https://github.com/psu-stewardship Penn State Digital Stewardship]
* [https://github.com/pulibrary Princeton University Library]
* [https://github.com/ryersonlibrary Ryerson University Library & Archives]
* [https://github.com/adsabs SAO/NASA Astrophysics Data System]
* [https://github.com/slub Saxon State and University Library Dresden]
* [https://github.com/scds Sherman Centre for Digital Scholarship, McMaster University]
* [https://github.com/sul-dlss Stanford University Digital Library]
* [https://github.com/UBCLIBSYS UBC Library Systems and IT]
* [https://github.com/ualbertalib University of Alberta Libraries]
* [https://github.com/ualibraries The University of Arizona Libraries]
* [https://github.com/ucalgarylib University of Calgary Libraries & Cultural Resources]
* [https://github.com/uc-data-services UC Berkeley Library Data & GIS Services]
* [https://github.com/UCLALibrary UCLA Library]
* [https://github.com/UCSCLibrary UCSC Library]
* [https://github.com/ucsdlib UCSD Library]
* [https://github.com/umd-lib University of Maryland Libraries]
* [https://github.com/UMNLibraries University of Minnesota Libraries]
* [https://github.com/UNC-Libraries University of North Carolina at Chapel Hill Libraries]
* [https://github.com/ui-libraries University of Iowa Libraries]
* [https://github.com/vculibraries Virginia Commonwealth University Libraries]
* [https://github.com/wellcomelibrary Wellcome Library]
* [https://github.com/yalemssa Manuscripts and Archives, Yale University Library]
* [https://github.com/yorkulibraries York University Libraries]

==Institutions with Non-GitHub open repositories==
* University of Florida: SobekCM software [http://sourceforge.net/directory/?q=sobekcm Sourceforge], [http://code.google.com/p/sobekcm/ Google code], [http://ufdc.ufl.edu/software UFDC institutional site]
* [http://eXtensibleCatalog.org eXtensible Catalog] repositories: [http://code.google.com/p/xcmetadataservicestoolkit/ Metadata Services Toolkit], [http://code.google.com/p/xcoaitoolkit/ OAI Toolkit], [http://code.google.com/p/xcncip2toolkit/ NCIP Toolkit] (all these on Google code), [http://drupal.org/project/xc Drupal Toolkit] (on drupal.org)
* [http://git.sitka.bclibraries.ca BC Libraries Cooperative]
* [https://bitbucket.org/uwlib/ UW Libraries]

==Other Library Organizations on GitHub==
* [https://github.com/projectblacklight Project Blacklight]
* [https://github.com/projecthydra Project Hydra]
* [https://github.com/islandora Islandora]
* [https://github.com/artefactual Artefactual], along with projects: [https://github.com/artefactual/atom AtoM], and [https://github.com/artefactual/archivematica Archivematica]
* [https://github.com/duraspace DuraSpace], along with projects: [https://github.com/dspace DSpace], [https://github.com/fcrepo4/ Fedora], and [https://svn.duraspace.org/view/duracloud/ DuraCloud (not yet on GitHub)]
* [https://github.com/hbz/ North Rhine-Westphalian Library Service Center (hbz)] and its service [https://github.com/lobid/ lobid]

* [https://github.com/pkp Public Knowledge Project], along with projects: [https://github.com/pkp/ojs Open Journal Systems], [https://github.com/pkp/ocs Open Conference Systems], and [https://github.com/pkp/omp Open Monograph Press]
* [https://github.com/internetarchive Internet Archive]
* [https://github.com/openlibrary Open Library Team]
* [https://github.com/scholarslab Scholars' Lab]
* [https://github.com/next-l Project Next-L]
* [http://librecat.org/ LibreCat Open Tools for Library and Research Services]
* [https://github.com/swissbib/ swissbib information services for Swiss university libraries and Swiss National library]
* [https://github.com/TEIC Text Encoding Initiative Consortium]

==Individuals on GitHub==
* [https://github.com/jronallo Jason Ronallo] North Carolina State University
* [https://github.com/cazzerson Jason Casden] North Carolina State University
* [https://github.com/jbfink John Fink] McMaster University
* [https://github.com/rgilmour70 Ron Gilmour] Ithaca College
* [https://github.com/mreidsma Matthew Reidsma] Grand Valley State University
* [https://github.com/mjsuhonos MJ Suhonos] Ryerson University Library & Archives
* [https://github.com/mjordan Mark Jordan] Simon Fraser University Library
* [https://github.com/jneubert Joachim Neubert] ZBW - Leibniz Information Centre for Economics
* [https://github.com/phette23 Eric Phetteplace] - California College of the Arts
* [https://github.com/barmintor Ben Armintor] Fedora 3, Blacklight, Hydra Projects
* [https://github.com/techbrarian Jason Bengtson] Houston Academy of Medicine/Texas Medical Center

Libraries Sharing Code

2016-02-26T20:41:31Z

Kayiwa: /* Institutions with Non-GitHub open repositories */

A number of libraries have organizational repositories in GitHub. These can be very valuable and we attempt to collect them here.

==Institutions on GitHub==
* [https://github.com/aadl Ann Arbor District Library]
* [https://github.com/BCLibCoop BC Libraries Cooperative]
* [https://github.com/BCLIbraries Boston College Libraries]
* [https://github.com/britishlibrary The British Library]
* [https://github.com/Brown-University-Library Brown University Library]
* [https://github.com/cca California College of the Arts]
* [https://github.com/csusm-library CSU San Marcos]
* [https://github.com/clcdpc Central Library Consortium]
* [https://github.com/chattlibrary Chattanooga Public Library] (currently empty)
* [https://github.com/cul Columbia University Libraries]
* [https://github.com/DarienLibrary Darien (CT) Library]
* [https://github.com/duke-libraries Duke University Libraries]
* [https://github.com/gwu-libraries George Washington University Libraries]
* [https://github.com/Georgetown-University-Libraries Georgetown University Libraries]
* [https://github.com/subugoe Göttingen State and University Library]
* [https://github.com/gvsulib Grand Valley State University Libraries]
* [https://github.com/GrinnellCollegeLibraries Grinnell College Libraries]
* [https://github.com/harvard-library Harvard University Library Technology Services]
* [https://github.com/LibraryOfCongress Library of Congress]
* [https://github.com/LibraryofVA Library of Virginia]
* [https://github.com/LincolnUniLTL Lincoln University Library Teaching and Learning] (New Zealand)
* [https://github.com/ndlib University of Notre Dame Hesburgh Libraries] (And [https://github.com/ndlibersa the CORAL stuff])
* [https://github.com/MontclairState Montclair State]
* [https://github.com/njstatelibrary New Jersey State Library]
* [https://github.com/nla National Library of Australia]
* [https://github.com/nims-library Scientific Information Office, National Institute for Materials Science (NIMS Library)]
* [https://github.com/NCSU-Libraries NCSU Libraries]
* [https://github.com/nypl The New York Public Library]
* [https://github.com/NYULibraries NYU Libraries]
* [https://github.com/RockefellerArchiveCenter Rockefeller Archive Center]
* [https://github.com/osulibraries Ohio State University Libraries]
* [https://github.com/osulp Oregon State University Libraries & Press]
* [https://github.com/psu-stewardship Penn State Digital Stewardship]
* [https://github.com/pulibrary Princeton University Library]
* [https://github.com/ryersonlibrary Ryerson University Library & Archives]
* [https://github.com/adsabs SAO/NASA Astrophysics Data System]
* [https://github.com/slub Saxon State and University Library Dresden]
* [https://github.com/scds Sherman Centre for Digital Scholarship, McMaster University]
* [https://github.com/sul-dlss Stanford University Digital Library]
* [https://github.com/UBCLIBSYS UBC Library Systems and IT]
* [https://github.com/ualbertalib University of Alberta Libraries]
* [https://github.com/ualibraries The University of Arizona Libraries]
* [https://github.com/ucalgarylib University of Calgary Libraries & Cultural Resources]
* [https://github.com/uc-data-services UC Berkeley Library Data & GIS Services]
* [https://github.com/UCLALibrary UCLA Library]
* [https://github.com/UCSCLibrary UCSC Library]
* [https://github.com/ucsdlib UCSD Library]
* [https://github.com/umd-lib University of Maryland Libraries]
* [https://github.com/UMNLibraries University of Minnesota Libraries]
* [https://github.com/UNC-Libraries University of North Carolina at Chapel Hill Libraries]
* [https://github.com/ui-libraries University of Iowa Libraries]
* [https://github.com/vculibraries Virginia Commonwealth University Libraries]
* [https://github.com/wellcomelibrary Wellcome Library]
* [https://github.com/yalemssa Manuscripts and Archives, Yale University Library]
* [https://github.com/yorkulibraries York University Libraries]

==Institutions with Non-GitHub open repositories==
* University of Florida: SobekCM software [http://sourceforge.net/directory/?q=sobekcm Sourceforge], [http://code.google.com/p/sobekcm/ Google code], [http://ufdc.ufl.edu/software UFDC institutional site]
* [http://eXtensibleCatalog.org eXtensible Catalog] repositories: [http://code.google.com/p/xcmetadataservicestoolkit/ Metadata Services Toolkit], [http://code.google.com/p/xcoaitoolkit/ OAI Toolkit], [http://code.google.com/p/xcncip2toolkit/ NCIP Toolkit] (all these on Google code), [http://drupal.org/project/xc Drupal Toolkit] (on drupal.org)
* [http://git.sitka.bclibraries.ca BC Libraries Cooperative]

==Other Library Organizations on GitHub==
* [https://github.com/projectblacklight Project Blacklight]
* [https://github.com/projecthydra Project Hydra]
* [https://github.com/islandora Islandora]
* [https://github.com/artefactual Artefactual], along with projects: [https://github.com/artefactual/atom AtoM], and [https://github.com/artefactual/archivematica Archivematica]
* [https://github.com/duraspace DuraSpace], along with projects: [https://github.com/dspace DSpace], [https://github.com/fcrepo4/ Fedora], and [https://svn.duraspace.org/view/duracloud/ DuraCloud (not yet on GitHub)]
* [https://github.com/hbz/ North Rhine-Westphalian Library Service Center (hbz)] and its service [https://github.com/lobid/ lobid]

* [https://github.com/pkp Public Knowledge Project], along with projects: [https://github.com/pkp/ojs Open Journal Systems], [https://github.com/pkp/ocs Open Conference Systems], and [https://github.com/pkp/omp Open Monograph Press]
* [https://github.com/internetarchive Internet Archive]
* [https://github.com/openlibrary Open Library Team]
* [https://github.com/scholarslab Scholars' Lab]
* [https://github.com/next-l Project Next-L]
* [http://librecat.org/ LibreCat Open Tools for Library and Research Services]
* [https://github.com/swissbib/ swissbib information services for Swiss university libraries and Swiss National library]
* [https://github.com/TEIC Text Encoding Initiative Consortium]

==Individuals on GitHub==
* [https://github.com/jronallo Jason Ronallo] North Carolina State University
* [https://github.com/cazzerson Jason Casden] North Carolina State University
* [https://github.com/jbfink John Fink] McMaster University
* [https://github.com/rgilmour70 Ron Gilmour] Ithaca College
* [https://github.com/mreidsma Matthew Reidsma] Grand Valley State University
* [https://github.com/mjsuhonos MJ Suhonos] Ryerson University Library & Archives
* [https://github.com/mjordan Mark Jordan] Simon Fraser University Library
* [https://github.com/jneubert Joachim Neubert] ZBW - Leibniz Information Centre for Economics
* [https://github.com/phette23 Eric Phetteplace] - California College of the Arts
* [https://github.com/barmintor Ben Armintor] Fedora 3, Blacklight, Hydra Projects
* [https://github.com/techbrarian Jason Bengtson] Houston Academy of Medicine/Texas Medical Center

2016 Conference Volunteers

2016-02-08T13:55:21Z

Kayiwa:

Code4Lib 2016 Volunteers sign-up page. As conference plans evolve, the page will be periodically updated with new opportunities to volunteer. When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.

For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.

== Welcome Wagon/Concierge ==

Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.
*
*

== Conference Logistics ==

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

Sunday:
* Katherine Lynch
* Lauren Gala
* Chad Nelson

Monday:
* Lauren Gala
*

== Preconference Setup ==

Help manage preconference sessions, setting up projectors, etc.

Sheraton Society Hill (Conference Hotel):
* Lauren Gala

Chemical Heritage Foundation:
* Anna Headley (CHF contact)
* Michelle DiMeo (CHF contact)

Franklin Hall:
* Scott Ziegler (venue contact at APS)

== Social Networking ==

Answering general questions on Twitter and IRC:
*
*

Ask questions on mic on behalf of community (because of distance, mic aversion, etc)

Tuesday:
*

Wednesday:
*

Thursday:
*

== Livestream ==
Volunteers for the livestream will assist the livestream technician with conferencee streaming. Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.

Tuesday AM:
*

Tuesday PM:
* Francis Kayiwa

Wednesday AM:
*

Wednesday PM:
*

Thursday AM:
*

== IRC (Technical) ==

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

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

==Registration Desk ==
Assists with handing out registration materials to attendees.

Monday AM (8:00-9:30):
* Shaun Ellis
* Katherine Lynch

Monday PM (12:00-1:30):
*
* Katherine Lynch

Tuesday AM (7:00-9:30):
* Lauren Gala
*

==MCs==

Tuesday AM:
* David Lacy

Tuesday PM:
* Shaun Ellis

Wednesday AM:
* Anna Headley

Wednesday PM:
* Dre

Thursday AM:
*

== 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:
* Francis Kayiwa
*

Tuesday PM:
* Lauren Gala
* Katherine Lynch

Wednesday AM:
* Lauren Gala
*

Wednesday PM:
* Lauren Gala
*

Thursday AM:
* Lauren Gala
*

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

[[Category: Code4Lib2016]]

2016 Conference Volunteers

2016-02-08T13:49:37Z

Kayiwa:

Code4Lib 2016 Volunteers sign-up page. As conference plans evolve, the page will be periodically updated with new opportunities to volunteer. When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.

For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.

== Welcome Wagon/Concierge ==

Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.
*
*

== Conference Logistics ==

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

Sunday:
* Katherine Lynch
* Lauren Gala
* Chad Nelson

Monday:
* Lauren Gala
*

== Preconference Setup ==

Help manage preconference sessions, setting up projectors, etc.

Sheraton Society Hill (Conference Hotel):
* Lauren Gala

Chemical Heritage Foundation:
* Anna Headley (CHF contact)
* Michelle DiMeo (CHF contact)

Franklin Hall:
* Scott Ziegler (venue contact at APS)

== Social Networking ==

Answering general questions on Twitter and IRC:
*
*

Ask questions on mic on behalf of community (because of distance, mic aversion, etc)

Tuesday:
*

Wednesday:
*

Thursday:
*

== Livestream ==
Volunteers for the livestream will assist the livestream technician with conferencee streaming. Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.

Tuesday AM:
*

Tuesday PM:
*

Wednesday AM:
*

Wednesday PM:
*

Thursday AM:
*

== IRC (Technical) ==

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

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

==Registration Desk ==
Assists with handing out registration materials to attendees.

Monday AM (8:00-9:30):
* Shaun Ellis
* Katherine Lynch

Monday PM (12:00-1:30):
*
* Katherine Lynch

Tuesday AM (7:00-9:30):
* Lauren Gala
*

==MCs==

Tuesday AM:
* David Lacy

Tuesday PM:
* Shaun Ellis

Wednesday AM:
* Anna Headley

Wednesday PM:
* Dre

Thursday AM:
*

== 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:
* Francis Kayiwa
*

Tuesday PM:
* Lauren Gala
* Katherine Lynch

Wednesday AM:
* Lauren Gala
*

Wednesday PM:
* Lauren Gala
*

Thursday AM:
* Lauren Gala
*

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

[[Category: Code4Lib2016]]

MDC

2015-07-14T15:54:03Z

Kayiwa: /* Code4Lib MDCV 2015 meetup */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib MDCV 2015 meetup===

August 11-12, 2015 - McKeldin Library, University of Maryland, College Park 

'''Organizing folks'''

(Please add your name if you are attending and willing to help organizing!)

Andrea Medina-Smith, Ben Wallberg, Bill Helman, Bohyun Kim, Bria Parker, Francis Kayiwa, Josh Westgard, Laura Wrubel, Neil M. Frau-Cortes

'''Details, schedule, and registration'''
* Coming up soon! To be announced early July.
* 8/11: Prepared talks (Morning), Unconference (Afternoon)
* 8/12: Hackathon and Workshops

Free to attend or for a fee? [[User:Brooke|Brooke]] ([[User talk:Brooke|talk]]) 05:18, 1 July 2015 (PDT)
: It's free to attend! :-) [[User:Edsu|Edsu]] ([[User talk:Edsu|talk]]) 06:36, 9 July 2015 (PDT)

'''20-minute talks - feel free to sign up'''
*
*
'''Unconference discussion topic - feel free to sign up'''

* DSpace and everything around the Dspace ecosystem. -- Ben Wallberg to lead
*
'''Hackathon ideas - feel free to post'''
*
*
'''Workshop topics - feel free to sign up'''
* All your Logs are belong to us.
A workshop on how to do central logging of server logs. using Elasticsearch, Logstash/lumberjack and Kibana. Users will leave with a basic understanding of how to use these three tools to look at logs of all sorts up to and including the tweets.
--Francis

*

== Last Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (UMB HS/HSL), [http://www.slideshare.net/bohyunkim/online-payment-for-your-library-and-stripe-as-an-example "Accepting Online Payment for Your Library and 'Stripe' as an Example"]
* Francis Kayiwa, [http://slides.com/franciskayiwa/monitoring-sucks#/ "Monitoring Sucks"]
* David Anderson (National Library of Medicine): "Linked Data at NLM"
* Ben Wallberg (UMD Libraries), "Research Services at UMD Libraries"
* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''5-minute lightning talks signups - on site'''
* see whiteboard in room 302

'''1.5 or 3 hour workshops - feel free to sign up'''

'''Practice jQuery, for those in workshop (1.5 or 3 hours)'''

'''Jason Griffey, Hacking on Hardware (3 hours):'''

Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and will deconstruct and then rebuild our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). The goal of the workshop will be to give you enough knowledge that you can build a simple sensor to measure something in your environment (noise, temperature, light, moisture) and to make you more comfortable with working with hardware. This session is designed for beginners who do not have experience with circuits, breadboards, Arduino, or other aspects of hardware hacking.

If you are planning to attend this hardware hacking afternoon, you will need to install a couple of things before you arrive to save time. Please download and install both the Arduino IDE 1.0.5 and the FTDI Drivers (serial drives for the Sparkfun Redboard), linked below. These will allow your laptop to communicate with the board.

'''Arduino IDE'''
*[http://arduino.cc/en/Main/Software IDE 1.0.5]
'''FTDI Drivers'''
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#windows---quick-and-easy Windows]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#mac Mac]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#linux Linux]

'''Kevin Ford, Gettting Started with the Bibframe Editor (1.5 hours):'''

Learn about, download, locally install, and tinker with the nascent Bibframe Editor (bfe) (https://github.com/lcnetdev/bfe). This workshop will provide an introduction to the Bibframe Editor, which, despite its name, is basically a generic, web-based RDF editor. All forms are dynamically generated from specially defined JSON-formatted [http://www.loc.gov/bibframe/docs/bibframe-profiles.html Bibframe Profiles], which you can customize with your own classes and properties to meet your needs. `bfe` also ships with a number of "look ups," which provide typeahead functionality that dynamically search remote value vocabularies, such as [http://id.loc.gov/authorities/names Names] and [http://id.loc.gov/authorities/subjects Subjects] in [http://id.loc.gov/ ID.LOC.GOV], and allow you to choose a value from a suggested set of values (you can also create your own look ups). After a brief introduction about `bfe`, we'll work to install it on your own laptop. We'll then learn a little about profiles by modifying a few existing ones. Time permitting, we'll look at creating a new "look up."

Preparing ahead of time?

Essential:
[http://nodejs.org/download/ node.js] OR [https://www.python.org/download/ Python 2.7]
(Do please try to have these installed before the workshop, otherwise we'll spend a minute or two installing node.js.)

Optional:
Git

'''Patrick Murray-John, Omeka under the hood (1.5 hours)'''

== Previous Meetings ==

'''When:''' Thursday, September 13th 2012 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

MDC

2015-07-11T23:44:40Z

Kayiwa: Added my ELK Workshop proposal

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib MDCV 2015 meetup===

August 11-12, 2015 - McKeldin Library, University of Maryland, College Park 

'''Organizing folks'''

(Please add your name if you are attending and willing to help organizing!)

Andrea Medina-Smith, Ben Wallberg, Bill Helman, Bohyun Kim, Bria Parker, Francis Kayiwa, Josh Westgard, Laura Wrubel, Neil M. Frau-Cortes

'''Details, schedule, and registration'''
* Coming up soon! To be announced early July.
* 8/11: Prepared talks (Morning), Unconference (Afternoon)
* 8/12: Hackathon and Workshops

Free to attend or for a fee? [[User:Brooke|Brooke]] ([[User talk:Brooke|talk]]) 05:18, 1 July 2015 (PDT)
: It's free to attend! :-) [[User:Edsu|Edsu]] ([[User talk:Edsu|talk]]) 06:36, 9 July 2015 (PDT)

'''20-minute talks - feel free to sign up'''
*
*
'''Unconference discussion topic - feel free to sign up'''
*
*
'''Hackathon ideas - feel free to post'''
*
*
'''Workshop topics - feel free to sign up'''
* All your Logs are belong to us.
A workshop on how to do central logging of server logs. using Elasticsearch, Logstash/lumberjack and Kibana. Users will leave with a basic understanding of how to use these three tools to look at logs of all sorts up to and including the tweets.
--Francis

*

== Last Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (UMB HS/HSL), [http://www.slideshare.net/bohyunkim/online-payment-for-your-library-and-stripe-as-an-example "Accepting Online Payment for Your Library and 'Stripe' as an Example"]
* Francis Kayiwa, [http://slides.com/franciskayiwa/monitoring-sucks#/ "Monitoring Sucks"]
* David Anderson (National Library of Medicine): "Linked Data at NLM"
* Ben Wallberg (UMD Libraries), "Research Services at UMD Libraries"
* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''5-minute lightning talks signups - on site'''
* see whiteboard in room 302

'''1.5 or 3 hour workshops - feel free to sign up'''

'''Practice jQuery, for those in workshop (1.5 or 3 hours)'''

'''Jason Griffey, Hacking on Hardware (3 hours):'''

Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and will deconstruct and then rebuild our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). The goal of the workshop will be to give you enough knowledge that you can build a simple sensor to measure something in your environment (noise, temperature, light, moisture) and to make you more comfortable with working with hardware. This session is designed for beginners who do not have experience with circuits, breadboards, Arduino, or other aspects of hardware hacking.

If you are planning to attend this hardware hacking afternoon, you will need to install a couple of things before you arrive to save time. Please download and install both the Arduino IDE 1.0.5 and the FTDI Drivers (serial drives for the Sparkfun Redboard), linked below. These will allow your laptop to communicate with the board.

'''Arduino IDE'''
*[http://arduino.cc/en/Main/Software IDE 1.0.5]
'''FTDI Drivers'''
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#windows---quick-and-easy Windows]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#mac Mac]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#linux Linux]

'''Kevin Ford, Gettting Started with the Bibframe Editor (1.5 hours):'''

Learn about, download, locally install, and tinker with the nascent Bibframe Editor (bfe) (https://github.com/lcnetdev/bfe). This workshop will provide an introduction to the Bibframe Editor, which, despite its name, is basically a generic, web-based RDF editor. All forms are dynamically generated from specially defined JSON-formatted [http://www.loc.gov/bibframe/docs/bibframe-profiles.html Bibframe Profiles], which you can customize with your own classes and properties to meet your needs. `bfe` also ships with a number of "look ups," which provide typeahead functionality that dynamically search remote value vocabularies, such as [http://id.loc.gov/authorities/names Names] and [http://id.loc.gov/authorities/subjects Subjects] in [http://id.loc.gov/ ID.LOC.GOV], and allow you to choose a value from a suggested set of values (you can also create your own look ups). After a brief introduction about `bfe`, we'll work to install it on your own laptop. We'll then learn a little about profiles by modifying a few existing ones. Time permitting, we'll look at creating a new "look up."

Preparing ahead of time?

Essential:
[http://nodejs.org/download/ node.js] OR [https://www.python.org/download/ Python 2.7]
(Do please try to have these installed before the workshop, otherwise we'll spend a minute or two installing node.js.)

Optional:
Git

'''Patrick Murray-John, Omeka under the hood (1.5 hours)'''

== Previous Meetings ==

'''When:''' Thursday, September 13th 2012 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

MDC

2015-07-11T23:38:45Z

Kayiwa: /* Code4Lib MDCV 2015 meetup */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib MDCV 2015 meetup===

August 11-12, 2015 - McKeldin Library, University of Maryland, College Park 

'''Organizing folks'''

(Please add your name if you are attending and willing to help organizing!)

Andrea Medina-Smith, Ben Wallberg, Bill Helman, Bohyun Kim, Bria Parker, Francis Kayiwa, Josh Westgard, Laura Wrubel, Neil M. Frau-Cortes

'''Details, schedule, and registration'''
* Coming up soon! To be announced early July.
* 8/11: Prepared talks (Morning), Unconference (Afternoon)
* 8/12: Hackathon and Workshops

Free to attend or for a fee? [[User:Brooke|Brooke]] ([[User talk:Brooke|talk]]) 05:18, 1 July 2015 (PDT)
: It's free to attend! :-) [[User:Edsu|Edsu]] ([[User talk:Edsu|talk]]) 06:36, 9 July 2015 (PDT)

'''20-minute talks - feel free to sign up'''
*
*
'''Unconference discussion topic - feel free to sign up'''
*
*
'''Hackathon ideas - feel free to post'''
*
*
'''Workshop topics - feel free to sign up'''
* All your Logs are belong to us. A workshop on how to do central logging using the ELK stack.
*

== Last Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (UMB HS/HSL), [http://www.slideshare.net/bohyunkim/online-payment-for-your-library-and-stripe-as-an-example "Accepting Online Payment for Your Library and 'Stripe' as an Example"]
* Francis Kayiwa, [http://slides.com/franciskayiwa/monitoring-sucks#/ "Monitoring Sucks"]
* David Anderson (National Library of Medicine): "Linked Data at NLM"
* Ben Wallberg (UMD Libraries), "Research Services at UMD Libraries"
* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''5-minute lightning talks signups - on site'''
* see whiteboard in room 302

'''1.5 or 3 hour workshops - feel free to sign up'''

'''Practice jQuery, for those in workshop (1.5 or 3 hours)'''

'''Jason Griffey, Hacking on Hardware (3 hours):'''

Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and will deconstruct and then rebuild our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). The goal of the workshop will be to give you enough knowledge that you can build a simple sensor to measure something in your environment (noise, temperature, light, moisture) and to make you more comfortable with working with hardware. This session is designed for beginners who do not have experience with circuits, breadboards, Arduino, or other aspects of hardware hacking.

If you are planning to attend this hardware hacking afternoon, you will need to install a couple of things before you arrive to save time. Please download and install both the Arduino IDE 1.0.5 and the FTDI Drivers (serial drives for the Sparkfun Redboard), linked below. These will allow your laptop to communicate with the board.

'''Arduino IDE'''
*[http://arduino.cc/en/Main/Software IDE 1.0.5]
'''FTDI Drivers'''
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#windows---quick-and-easy Windows]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#mac Mac]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#linux Linux]

'''Kevin Ford, Gettting Started with the Bibframe Editor (1.5 hours):'''

Learn about, download, locally install, and tinker with the nascent Bibframe Editor (bfe) (https://github.com/lcnetdev/bfe). This workshop will provide an introduction to the Bibframe Editor, which, despite its name, is basically a generic, web-based RDF editor. All forms are dynamically generated from specially defined JSON-formatted [http://www.loc.gov/bibframe/docs/bibframe-profiles.html Bibframe Profiles], which you can customize with your own classes and properties to meet your needs. `bfe` also ships with a number of "look ups," which provide typeahead functionality that dynamically search remote value vocabularies, such as [http://id.loc.gov/authorities/names Names] and [http://id.loc.gov/authorities/subjects Subjects] in [http://id.loc.gov/ ID.LOC.GOV], and allow you to choose a value from a suggested set of values (you can also create your own look ups). After a brief introduction about `bfe`, we'll work to install it on your own laptop. We'll then learn a little about profiles by modifying a few existing ones. Time permitting, we'll look at creating a new "look up."

Preparing ahead of time?

Essential:
[http://nodejs.org/download/ node.js] OR [https://www.python.org/download/ Python 2.7]
(Do please try to have these installed before the workshop, otherwise we'll spend a minute or two installing node.js.)

Optional:
Git

'''Patrick Murray-John, Omeka under the hood (1.5 hours)'''

== Previous Meetings ==

'''When:''' Thursday, September 13th 2012 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

2015 During the Conference Volunteers

2015-02-05T14:26:58Z

Kayiwa:

code4lib 2015 During the Conference Volunteers



== Preconference Setup Help ==

Help manage preconference sessions, setting up projectors, etc.

* John Sarnowski (at ResCarta)
* Whitni Watkins (at NimbleLibrarian)
* Christina Harlow (at cm_harlow)
* Eric Frierson (at frierson)

== Welcome Wagon Committee ==

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

* Becky Yoose (b.yoose at google)

== Social Networking ==
Responsible for non-IRC social networking presence.

1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.

Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.

*Whitni Watkins (at NimbleLibrarian)
* Christina Harlow (at cm_harlow)

== Beverage Share Setup/Teardown ==

Help set up and clean up after the Tuesday event at the Ebay offices.

* Karen Estlund - setup
* John Sarnowski - clean up (at ResCarta)
* Dominic Bordelon - clean up
* Whitni Watkins - setup (at NimbleLibrarian)
* Ben Armintor - both/either (barmintor)
* Bobbi Fox - setup
* Matt Critchlow - clean up
* Francis Kayiwa - clean up

== IRC Helpers ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

* Chad Nelson (bibliotechy)
* Mx Matienzo (anarchivist; as needed)

One of the easiest ways to participate is to go to [http://webchat.freenode.net/ Freenode Webchat] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "#code4lib" as the "Channel".

If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.

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

* Mx Matienzo (anarchivist)

==Registration Desk Volunteers==

'''Monday'''
* John Sarnowski (at ResCarta)
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.
'''Tuesday'''
* Christina Harlow (at cm_harlow)
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.
'''Wednesday'''
* Christina Harlow (at cm_harlow)
* Bobbi Fox

==Video Streaming==
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.

You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.

'''Tuesday AM'''

* Ashley Blewer (at ablwr)
* Steven Anderson (at scande3)

'''Tuesday PM'''

* Ashley Blewer (at ablwr)
* Steven Anderson (at scande3)

'''Wednesday AM'''

* Ashley Blewer (at ablwr)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

'''Wednesday PM'''

* Ashley Blewer (at ablwr)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

'''Thursday AM'''

* Ashley Blewer (at ablwr, go big or go home)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

==MCs==

'''Tuesday AM'''
*Terry R., likes to put birds on things

'''Tuesday PM'''
*Eric, mumbler extraordinaire

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

'''Wednesday PM'''
*Cary, taller than Becky, will not sing.

'''Thursday AM'''

== Session Timer Volunteers ==

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

'''Schedule for Session Timers'''

'''Tuesday AM'''

* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)
* Sarah Simpkin (at sarahsimpkin)

'''Tuesday PM'''
*Maura Carbone
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)

'''Wednesday AM'''
* John Sarnowski (at ResCarta)
* Sarah Simpkin (at sarahsimpkin)

'''Wednesday PM'''
* Dominic Bordelon

'''Thursday AM'''
* Eric Phetteplace (at phette23)

== Raffles ==

== Whatever Else Needs to be Done ==

* Sarah Simpkin (at sarahsimpkin)

[[Category: Code4Lib2015]]

2015 During the Conference Volunteers

2015-02-05T14:25:55Z

Kayiwa: /* Session Timer Volunteers */

code4lib 2015 During the Conference Volunteers



== Preconference Setup Help ==

Help manage preconference sessions, setting up projectors, etc.

* John Sarnowski (at ResCarta)
* Whitni Watkins (at NimbleLibrarian)
* Christina Harlow (at cm_harlow)
* Eric Frierson (at frierson)

== Welcome Wagon Committee ==

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

* Becky Yoose (b.yoose at google)

== Social Networking ==
Responsible for non-IRC social networking presence.

1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.

Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.

*Whitni Watkins (at NimbleLibrarian)
* Christina Harlow (at cm_harlow)

== Beverage Share Setup/Teardown ==

Help set up and clean up after the Tuesday event at the Ebay offices.

* Karen Estlund - setup
* John Sarnowski - clean up (at ResCarta)
* Dominic Bordelon - clean up
* Whitni Watkins - setup (at NimbleLibrarian)
* Ben Armintor - both/either (barmintor)
* Bobbi Fox - setup
* Matt Critchlow - clean up

== IRC Helpers ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

* Chad Nelson (bibliotechy)
* Mx Matienzo (anarchivist; as needed)

One of the easiest ways to participate is to go to [http://webchat.freenode.net/ Freenode Webchat] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "#code4lib" as the "Channel".

If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.

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

* Mx Matienzo (anarchivist)

==Registration Desk Volunteers==

'''Monday'''
* John Sarnowski (at ResCarta)
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.
'''Tuesday'''
* Christina Harlow (at cm_harlow)
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.
'''Wednesday'''
* Christina Harlow (at cm_harlow)
* Bobbi Fox

==Video Streaming==
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.

You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.

'''Tuesday AM'''

* Ashley Blewer (at ablwr)
* Steven Anderson (at scande3)

'''Tuesday PM'''

* Ashley Blewer (at ablwr)
* Steven Anderson (at scande3)

'''Wednesday AM'''

* Ashley Blewer (at ablwr)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

'''Wednesday PM'''

* Ashley Blewer (at ablwr)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

'''Thursday AM'''

* Ashley Blewer (at ablwr, go big or go home)
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)

==MCs==

'''Tuesday AM'''
*Terry R., likes to put birds on things

'''Tuesday PM'''
*Eric, mumbler extraordinaire

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

'''Wednesday PM'''
*Cary, taller than Becky, will not sing.

'''Thursday AM'''

== Session Timer Volunteers ==

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

'''Schedule for Session Timers'''

'''Tuesday AM'''

* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)
* Sarah Simpkin (at sarahsimpkin)

'''Tuesday PM'''
*Maura Carbone
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)

'''Wednesday AM'''
* John Sarnowski (at ResCarta)
* Sarah Simpkin (at sarahsimpkin)

'''Wednesday PM'''
* Dominic Bordelon

'''Thursday AM'''
* Eric Phetteplace (at phette23)

== Raffles ==

== Whatever Else Needs to be Done ==

* Sarah Simpkin (at sarahsimpkin)

[[Category: Code4Lib2015]]

2015 Preconference Proposals

2015-01-28T16:58:40Z

Kayiwa: mail address update

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 - sysadmin/developer
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
# Liza Harrell-Edge - end-user
# Jessica Venlet - end-user/archivist (can be there in the afternoon)
# Andrew Berger - "digital" archivist

====[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 , fkayiwa at umd dot edu

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

''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 During the Conference Volunteers

2015-01-22T10:56:13Z

Kayiwa:

code4lib 2015 During the Conference Volunteers



== Welcome Wagon Committee ==

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

* Becky Yoose (b.yoose at google)

== Social Networking ==
Responsible for non-IRC social networking presence.

1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.

Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.

== Beverage Share Setup/Teardown ==

Help set up and clean up after the Tuesday event at the Ebay offices.

== IRC Helpers ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "code4lib" as the "Channel".

If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.

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

* Mx Matienzo (anarchivist)

==Registration Desk Volunteers==

'''Monday'''

'''Tuesday'''

'''Wednesday'''

==MCs==

'''Tuesday AM'''

'''Tuesday PM'''

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

'''Wednesday PM'''

'''Thursday AM'''

== Session Timer Volunteers ==

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

'''Schedule for Session Timers'''

'''Tuesday AM'''

* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)

'''Tuesday PM'''

'''Wednesday AM'''

'''Wednesday PM'''

'''Thursday AM'''

== Raffles ==

== Whatever Else Needs to be Done ==

[[Category: Code4Lib2015]]

2015 Craft Drinkup

2015-01-20T22:02:06Z

Kayiwa:

When: Tuesday, February 10th - 7pm - 10pm (ish)

Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201

The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer, soda, and other drinks with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.

While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages.

This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share.

Please Note: The space must be cleaned up and all folks gone no later than 11pm.

Space is limited to the first 200 people who register.

== Signup ==
Please sign up below to share the brews and bottles you're thinking of bringing along and make any special requests (but don't expect that your wishes will be granted).

{| class="wikitable"
|-
! Name !! Bringing !! Wanting
|-
| Esmé Cowles || Cigar City 110K+OT Batch #7 or Marshal Zhukov, Homebrew Imperial Saison || Any saison or sour!
|-
| Francis Kayiwa || (at least the following) Boulevard Quad Bourbon Barrel, Weyebacher Althea || <strike> Scotty Karate </strike> barleywines and any porters
|-
| Becky Yoose || Non-alcoholic options: I have access to craft sodas from Millstream, Sprechers, Stevens Point - '''ping me at b.yoose at gmail if you have a wish list!''' Otherwise, I'll buy whatever's available in PDX|| N/A drinks :c) Melon soda (not Ramune) greatly appreciated
|-
| Tania Fersenheim || Something from Pretty Things || ...
|-
| Ben Armintor || BCS Pappy Van Winkle, Dark Lord 2009, Black Tuesday || ...
|-
| Justin Coyne || Surly Darkness? || ...
|-
| Whitni Watkins|| Non-alcoholic Ginger beer options: at least Reed's & Saranac Lake. Potentially one other local brewed Ginger beer. If you have a request from Upstate NY HMU whitni.watkins at gmail || Ginger Beers & Ales specifically: Fentimans, River City, Bundaberg and Blenheim Red Hot
|-
| Sarah Simpkin || Accepting requests for tasty Quebecois beers -- [https://brouehaha.com/en/nos-bieres/ see this list for breweries]. Otherwise will grab a small selection. Contact me at sarahsimpkin at gmail.com :-) || Hefeweizen-y beers appreciated
|-
| Your Name here || Your Brews Here || Wish List...
|}

2015 Craft Drinkup

2015-01-17T00:58:31Z

Kayiwa:

When: Tuesday, February 10th - 7pm - 10pm (ish)

Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201

The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer, soda, and other drinks with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.

While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages.

This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share.

Please Note: The space must be cleaned up and all folks gone no later than 11pm.

Space is limited to the first 200 people who register.

== Signup ==
Please sign up below to share the brews and bottles you're thinking of bringing along and make any special requests (but don't expect that your wishes will be granted).

{| class="wikitable"
|-
! Name !! Bringing !! Wanting
|-
| Esmé Cowles || Cigar City 110K+OT Batch #7 or Marshal Zhukov, Homebrew Imperial Saison || Any saison or sour!
|-
| Francis Kayiwa || (at least the following) Boulevard Quad Bourbon Barrel, Weyebacher Althea || Scotty Karate and any porters
|-
| Becky Yoose || Non-alcoholic options: I have access to craft sodas from Millstream, Sprechers, Stevens Point - '''ping me at b.yoose at gmail if you have a wish list!''' Otherwise, I'll buy whatever's available in PDX|| N/A drinks :c) Melon soda (not Ramune) greatly appreciated
|-
| Tania Fersenheim || Something from Pretty Things || ...
|-
| Ben Armintor || BCS Pappy Van Winkle, Dark Lord 2009, Black Tuesday || ...
|-
| Your Name here || Your Brews Here || Wish List...
|}

2015 Craft Drinkup

2015-01-16T15:52:24Z

Kayiwa:

2015 Craft Drinkup

2015-01-16T15:50:22Z

Kayiwa:

2016 Hosting Proposals

2015-01-09T21:35:52Z

Kayiwa: @yo_bj caught the mistakes.

'''Schedule'''

Proposal period opens: January 9th 2015

Proposal period ends: February 20th 2015

Voting opens: February 23rd, 2015

Voting closes: March 6th, 2015

Please list your proposal below:

[[Category:Code4Lib2016]]

2016 Hosting Proposals

2015-01-09T02:15:18Z

Kayiwa:

'''Schedule'''

Proposal period opens: January 9th 2015

Proposal period ends: February 9th 2015

Voting opens: February 9th 2015

Voting closes: February 12th 2015

Please list your proposal below:

[[Category:Code4Lib2016]]

How To Plan A Code4LibCon

2015-01-09T02:11:19Z

Kayiwa: /* Calls for Hosting */

* Apply to be a host

* Consider your action plan
** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.
** 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: Always an issue it seems. 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. 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.
*** make sure VPN is allowed
** 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.
** 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
** 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 approved by the community
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]
* Invite the community to help with
* 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]

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

==Gender Diversity & Minority Scholarship Committee==
The scholarship committee is a self-selected group that manages the gender diversity & minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.

===Suggestions received===
* Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) & relevant sections? & student chapter

===Process===
# Put out a call
# Receive and coordinate applications
# Distribute applications to the committee
# Select awardees
# Inform selected candidates
# Notify unsuccessful candidates
# Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )
# Hosts work with awardees on reimbursement, registration, etc.
# Follow up with awardees after the conference -- receive report, ask for suggestions, etc.

== Program Committtee==
The program committee is a self-selected group that manages talk proposals and other aspects of the program.
The process works something like this:

# Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.
# People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)
#* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)
# After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.
# After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.

===Program Voting===
Pre-conf voting may need to take place if there are more proposals than spaces.

Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly
explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.

There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.

If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.

===Guidelines===
For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:
* Max 2 presenters per talk (this should be checked at the proposal stage)
* Max 1 talk per person
* (at least) 15% talks to be decided by the program committee with "diversity" in mind. Diversity may be any of these (not an exhaustive list):
** first-time presenter (should be major consideration)
** gender
** visible minority
** technology/tool

Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].

Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.

===Schedule===
While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.

===Keynoter logistics===

See [[Keynote Committee Duties]].

===Talk Acceptance Letter (samples)===

<pre>
Dear <<first name last name>>,

On behalf of the Code4Lib Program Planning Committee, I am pleased to
notify you that your proposal, <<proposal title>> has been accepted for
the Code4Lib <<year>> in <<location>>. Please reply to this message to
confirm your intention to present the approved session at the Conference.
If at any time in the future you need to bow out or have any program
changes, please notify us immediately. You will be sent a letter of
agreement soon.

The schedule for the conference is here:

http://code4lib.org/conference/2011/schedule

You will have 20 minutes for your talk, including questions and answers.
A quick transition between speakers will be necessary.

It is very important that you focus your presentation on the more unique
and technical aspects of your topic whenever possible. Although Code4Lib
attendees come from many different work environments, they attend Code4Lib
events for information technology education.

Experts like you are the heart of Code4Lib. We really appreciate your contribution
and look forward to working with you.

Sincerely,

</pre>

===Talk Rejection Letter (sample)===
<pre>
I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:

- The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.
- Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special "Ask Anything" (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.

Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.
Roy
</pre>

== Sponsorship Committee ==
===Sample Sponsorship Request Letter===
As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.

Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and
information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from
http://www.code4lib.org/conference/

Our <> conference will be held in <> from <>. Be a part of this library success story by underwriting the conference!

We have several sponsorship levels:

<>
I look forward to hearing from you, and can be reached at <>.

Best,

<>
http://code4lib.org/

== Book Giveaway Committee ==
Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.

Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).

Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.

== T-shirt Committee ==
Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.

Example: [[2013 t-shirt design proposals]]

Propose to add additional restrictions:
* should not be a designed used previously (do we have an archive of previous designs somewhere?)
* unique (cannot be bought online already)
* design should include "code4lib" and conference year in design, city optional

== Money==
* [[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

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

=== Emails to send out ===

==== Quick orientation email for newer folks ====

Send out at least a week in advance before conference...

We're in the last few days before the conference begins, and for a good number of you,
this will be your first code4lib. Here is some information to help you navigate through
the conference craziness next week:

- Social Activities<insert link to SA page>: There's a lot going on outside of the sessions,
and this page has information about various gatherings, events, meals, etc. One activity I
want to highlight is the Newcomer dinner<insert link to SA page> that will be on
<insert date of dinner>. There are still a lot of great restaurants left on the list, and this
is your chance to meet folks you might otherwise not get a chance to talk to at the conference.
Read the guidelines on the wiki, and pick your restaurant.

(Public service announcement: for those of you who have signed up for the dinner already, make
sure that there's a designated leader for organizing reservations and people herding.)

- Hospitality Suite: For some of the events listed on the Social Activities page, you will see
the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside
of sessions (or taking a break from sessions). The location of the Suite is usually announced
through various means, including the wiki, IRC and Twitter.

- IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag
for conference related stuff. The IRC channel<insert link to IRC page> is #code4lib, and there
will be volunteers at the conference who would be more than happy to help you with IRC.

- For my last item, give the following a read:<insert links to appropriate pages>

-- How to hack code4lib
-- CodeofConduct4lib
-- Zoia, #code4lib's IRC bot

If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify
themselves as first timers and "old timers" as well, if you're into classification and stuff. ;-)

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

To: ilines@freenode.net

Hello,

I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week.
Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead
to avoid running up against the connection limit. Would it be possible to raise the cap
for us during the conference? Details follow.

Conference: code4lib 2010 < http://code4lib.org/conference/2010/ >
Dates: February 22-26, 2010
Attendees: 250
Location: Renaissance Asheville Hotel, Asheville, NC
IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block

We encourage in-channel participation, so we expect a high percentage of attendees to
be connected at once. We'll also have two or three channel bots connected from the
conference for the lobby monitors.

Please let me know if you need any further information, and thanks very much for
your help!

Michael

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===
# Water at the podium
# 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
# IRC Monitor for podium during speaker changes?

===Photography===

* Consider different colored lanyards to articulate personal photography preferences.

=== Video ===
# live stream is awesome
# join.me ??
# YouTube Live, youtube.com/code4lib

=== 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===
* (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] 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, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.

* 2008:
* 2009:
* 2010:
* 2011: March 5, 2010
* 2012:
* 2013: Jan 22, 2012
* 2014: January 27, 2013
* 2015: January 29, 2014
* 2016:

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

2016 Hosting Proposals

2015-01-09T01:41:37Z

Kayiwa: Created page with "'''Schedule''' Proposal period opens: January 9th 2015 Proposal period ends: February 9th 2015 Voting opens: February 9th 2015 Voting closes: February 12th 2015 Please li..."

'''Schedule'''

Proposal period opens: January 9th 2015

Proposal period ends: February 9th 2015

Voting opens: February 9th 2015

Voting closes: February 12th 2015

Please list your proposal below:

2015 Preconference Proposals

2014-11-17T20:47:08Z

Kayiwa: /* Intro to Docker */

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

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

=== Proposal formatting guidelines: ===
<pre>

=== Preconference Title: ===

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

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

Abstract

''Interested in Attending''

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

#
#
#

</pre>

== Pre-conference Proposals ==

Post your ideas here!

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

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

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

''Interested in Attending''

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

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

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

'''Half Day [Afternoon]'''

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

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

''Interested in Attending''

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

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

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

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

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

''Interested in Attending''

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

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

=== Replace yourself with a painfully complex bash script...or try Ansible ===
'''Half Day [Morning]'''

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

Abstract:

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

''Interested in Attending''

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

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

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

Abstract:

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

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia

=== Code Retreat ===
'''Full Day'''

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

Abstract:

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

''Interested in Attending''

# Mike Giarlo
#
#
=== Presentations workshop ===

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

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

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

''Interested in Attending''

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

#Vicky Steeves
#
#

=== Dive into Hydra ===

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

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

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

''Interested in Attending''

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

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

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

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

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

Abstract

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

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

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

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

''Interested in Attending''

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

'''Full day'''
#
#
#

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

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

=== Linked Data Workshop ===

One of:
'''"Half Day [morning]"'''

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

Abstract:

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

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

# Logan Cox
# Ray Schwartz
#

=== Code4Arc ===

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

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

Abstract:

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

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

The schedule may include the following:

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

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

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

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

# Laney McGlohon - developer
#
#

=== Fail4Lib 2015 ===
'''Half Day [TBD, probably afternoon]'''

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

Abstract:

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

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

The schedule may include the following:

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

''Interested in attending''

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

# Ray Schwartz
#
#

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

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

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

Abstract

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

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

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

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

''Interested in Attending''

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

# Megan Kudzia
#
#

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

'''Half Day [Whenever]'''

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

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

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

''Interested in Attending''

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

# Peggy Griesinger
# Ray Schwartz
#

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

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

Abstract

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

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

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

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

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

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

''Interested in Attending''

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

# Ray Schwartz
#
#

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

'''Half Day [Whenever]'''

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

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

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

''Interested in Attending''

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

#
#
#

=== Visualizing Library Data ===

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

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

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

''Interested in Attending''

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

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

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

'''Half Day [Afternoon]'''

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

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

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

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

#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

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

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

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

# Ranti Junus
# Jean Rainwater
# Mita Williams

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-11-17T20:44:40Z

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

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

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

=== Proposal formatting guidelines: ===
<pre>

=== Preconference Title: ===

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

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

Abstract

''Interested in Attending''

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

#
#
#

</pre>

== Pre-conference Proposals ==

Post your ideas here!

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

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

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

''Interested in Attending''

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

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

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

'''Half Day [Afternoon]'''

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

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

''Interested in Attending''

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

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

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

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

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

''Interested in Attending''

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

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

=== Replace yourself with a painfully complex bash script...or try Ansible ===
'''Half Day [Morning]'''

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

Abstract:

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

''Interested in Attending''

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

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

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

Abstract:

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

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia

=== Code Retreat ===
'''Full Day'''

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

Abstract:

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

''Interested in Attending''

# Mike Giarlo
#
#
=== Presentations workshop ===

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

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

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

''Interested in Attending''

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

#Vicky Steeves
#
#

=== Dive into Hydra ===

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

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

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

''Interested in Attending''

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

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

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

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

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

Abstract

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

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

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

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

''Interested in Attending''

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

'''Full day'''
#
#
#

'''Morning'''
# Ranti Junus
#
#

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

=== Linked Data Workshop ===

One of:
'''"Half Day [morning]"'''

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

Abstract:

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

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

# Logan Cox
# Ray Schwartz
#

=== Code4Arc ===

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

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

Abstract:

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

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

The schedule may include the following:

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

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

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

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

# Laney McGlohon - developer
#
#

=== Fail4Lib 2015 ===
'''Half Day [TBD, probably afternoon]'''

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

Abstract:

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

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

The schedule may include the following:

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

''Interested in attending''

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

# Ray Schwartz
#
#

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

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

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

Abstract

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

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

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

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

''Interested in Attending''

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

# Megan Kudzia
#
#

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

'''Half Day [Whenever]'''

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

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

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

''Interested in Attending''

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

# Peggy Griesinger
# Ray Schwartz
#

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

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

Abstract

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

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

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

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

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

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

''Interested in Attending''

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

# Ray Schwartz
#
#

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

'''Half Day [Whenever]'''

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

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

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

''Interested in Attending''

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

#
#
#

=== Visualizing Library Data ===

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

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

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

''Interested in Attending''

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

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

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

'''Half Day [Afternoon]'''

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

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

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

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

#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

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

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

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

# Ranti Junus
# Jean Rainwater
#

[[Category:Code4Lib2015]]

2015 Prepared Talk Proposals

2014-10-31T20:12:23Z

Kayiwa:

'''DRAFT ONLY'''

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

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

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

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

'''Proposals for Prepared Talks:'''

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

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
==Drupal 8 — Evolution & Revolution==

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

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

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

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

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

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

==The Impossible Search: Pulling data form unknown sources==

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

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

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

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

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

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

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

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

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

== Categorizing Records with Random Forests ==

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

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

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

== PDF metadata extraction for academic literature ==

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

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

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

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

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

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

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

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone. Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation (user testing in Undergrad Library) of interface design that would provide optimal user experience for receiving recommendations and navigation of the book stacks as a context to recommendations. Implications of research and development include best practice recommendations for interface development based on the formative user studies (e.g. communicating what works in this area, and what does not), further – based on the back end API developed for Topic Space, grant staff created web based recommendations that could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces library wide.

The recommender references both shelf locations of an item as well as other items circulation counts to provide recommendations. Outcomes of the grant include the availability of the Topic Spaces module on the Android Play store (select Undergrad library for Topic Space module: https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva ) and an experimental ([http://backbonejs.org/ Backbone.js]) Topic Space web app: http://minrva-dev.library.illinois.edu

== Leveling Up Your Git Workflow ==

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

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

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

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

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

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

2015 Preconference Proposals

2014-09-16T15:44:44Z

Kayiwa: /* Intro to Docker */

2015 Preconference Proposals

2014-09-16T15:43:13Z

Kayiwa: /* Intro to Docker */

2015 Invited Speakers Nominations

2014-09-09T17:34:04Z

Kayiwa:

Nominations for invited speakers/keynotes for Code4Lib 2015. 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__

==Andromeda Yelton==

Re-nominating last year's runner up in the keynote speaker voting and yanking/modding last year's short description. Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. Member of the LITA Board of Directors and advisor for Ada Initiative. http://andromedayelton.com/about/

==Mark Matienzo==

Mark is the director of Technology at DPLA. He is however much more than that. He has worked tirelessly as an archivist and technologist solving many problems in the library domain. While his leadership style shows up through service. It is time to actually listen to him for more than his oft moving 5 minute Lightning Talks. [[http://matienzo.org/ Mark Matienzo]]

[[Category:Code4Lib2015]]

MDC

2014-08-12T19:42:21Z

Kayiwa: /* Code4Lib DC 2014 unconference */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. We're looking forward to a 2013 of the same calibre. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (UMB HS/HSL), [http://www.slideshare.net/bohyunkim/online-payment-for-your-library-and-stripe-as-an-example "Accepting Online Payment for Your Library and 'Stripe' as an Example"]
* Francis Kayiwa, [http://slides.com/franciskayiwa/monitoring-sucks#/ "Monitoring Sucks"]
* David Anderson (National Library of Medicine): "Linked Data at NLM"
* Ben Wallberg (UMD Libraries), "Research Services at UMD Libraries"
* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''5-minute lightning talks signups - on site'''
* see whiteboard in room 302

'''1.5 or 3 hour workshops - feel free to sign up'''

'''Practice jQuery, for those in workshop (1.5 or 3 hours)'''

'''Jason Griffey, Hacking on Hardware (3 hours):'''

Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and will deconstruct and then rebuild our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). The goal of the workshop will be to give you enough knowledge that you can build a simple sensor to measure something in your environment (noise, temperature, light, moisture) and to make you more comfortable with working with hardware. This session is designed for beginners who do not have experience with circuits, breadboards, Arduino, or other aspects of hardware hacking.

If you are planning to attend this hardware hacking afternoon, you will need to install a couple of things before you arrive to save time. Please download and install both the Arduino IDE 1.0.5 and the FTDI Drivers (serial drives for the Sparkfun Redboard), linked below. These will allow your laptop to communicate with the board.

'''Arduino IDE'''
*[http://arduino.cc/en/Main/Software IDE 1.0.5]
'''FTDI Drivers'''
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#windows---quick-and-easy Windows]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#mac Mac]
*[https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers#linux Linux]

'''Kevin Ford, Gettting Started with the Bibframe Editor (1.5 hours):'''

Learn about, download, locally install, and tinker with the nascent Bibframe Editor (bfe) (https://github.com/lcnetdev/bfe). This workshop will provide an introduction to the Bibframe Editor, which, despite its name, is basically a generic, web-based RDF editor. All forms are dynamically generated from specially defined JSON-formatted [http://www.loc.gov/bibframe/docs/bibframe-profiles.html Bibframe Profiles], which you can customize with your own classes and properties to meet your needs. `bfe` also ships with a number of "look ups," which provide typeahead functionality that dynamically search remote value vocabularies, such as [http://id.loc.gov/authorities/names Names] and [http://id.loc.gov/authorities/subjects Subjects] in [http://id.loc.gov/ ID.LOC.GOV], and allow you to choose a value from a suggested set of values (you can also create your own look ups). After a brief introduction about `bfe`, we'll work to install it on your own laptop. We'll then learn a little about profiles by modifying a few existing ones. Time permitting, we'll look at creating a new "look up."

Preparing ahead of time?

Essential:
[http://nodejs.org/download/ node.js] OR [https://www.python.org/download/ Python 2.7]
(Do please try to have these installed before the workshop, otherwise we'll spend a minute or two installing node.js.)

Optional:
Git

'''Patrick Murray-John, Omeka under the hood (1.5 hours)'''

== Last Meeting ==

'''When:''' Thursday, September 13th 2012 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

== Previous Meetings ==
''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

MDC

2014-07-22T19:00:47Z

Kayiwa: /* Code4Lib DC 2014 unconference */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. We're looking forward to a 2013 of the same calibre. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (Univ. of Maryland, Baltimore): "Where to start when your library wants an online payment option"
* Francis Kayiwa, "Monitoring Sucks"

'''5-minute talks - feel free to sign up'''

* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''1.5 or 3 hour workshops - feel free to sign up'''

* Jason Griffey, Hacking on Hardware (3 hours): Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and building our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). If you are planning to attend this hardware hacking afternoon, you will need to have the Arduino IDE 1.0.5 installed. The IDE can be downloaded from http://arduino.cc/en/Main/Software.

== Last Meeting ==

'''When:''' Thursday, September 13th 2012 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

== Previous Meetings ==
''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

2015 Conference Committees

2014-07-02T20:25:21Z

Kayiwa: /* Whatever Committee */

= Code4Lib 2015 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact to each committee.

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

Need about 2 months to get books shipped to the conference location.

*

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

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

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

* mx matienzo
* cbeer
* Tod Olson
* [[User:Cynthia|Arty]]

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Sarah Shealy - v
* Ruth Kitchin Tillman
* Francis Kayiwa

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Becky Yoose (committee member 4 life)

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

== Streaming Video Committee ==

*[[User:highermath|Cary Gordon]] has equipment and domain knowledge to share.
*[[User:RileyChilds|Riley Childs]] has Knowledge and the YouTube Account credentials

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

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa

== Wifi / Electrical / IRC ==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2015]]

2015 Conference Committees

2014-07-02T20:24:42Z

Kayiwa: /* Scholarships Committee */

= Code4Lib 2015 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact to each committee.

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

Need about 2 months to get books shipped to the conference location.

*

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

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

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

* mx matienzo
* cbeer
* Tod Olson
* [[User:Cynthia|Arty]]

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Sarah Shealy - v
* Ruth Kitchin Tillman
* Francis Kayiwa

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Becky Yoose (committee member 4 life)

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

== Streaming Video Committee ==

*[[User:highermath|Cary Gordon]] has equipment and domain knowledge to share.
*[[User:RileyChilds|Riley Childs]] has Knowledge and the YouTube Account credentials

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

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

== Wifi / Electrical / IRC ==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2015]]