Code4Lib - User contributions [en]

Code4Lib 2022 Conference Committees

2021-09-20T14:02:41Z

JerryYarnetsky: added my name as volunteer

= 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.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
* Your Name Here - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - 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
* 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
* Your Name Here - 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]]

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

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - 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]]

2018 Code4Lib Midwest Meeting

2018-06-06T14:32:11Z

JerryYarnetsky: /* Getting Here/Parking */

===Location===
[http://lib.miamioh.edu King Library]

Miami University of Ohio

[https://www.google.com/maps/place/Edgar+W+King+Library/@39.5087909,-84.7401835,17 Google Maps]

==Call for proposals==
To help us make sure we have a room for you to present in, we encourage you to submit a proposal by the end of March, 2018. Unless we get a tremendous amount of proposals we do not anticipate rejecting submissions.

[https://goo.gl/forms/HYisy6ihaPlWR2Lo2 Link to submit your presentation]

==Registration==
Registration for this conference is free and does not require joining a national organization. Due to space limits, registration will be limited to 50 participants. Similar to the national Code4lib, we have a meal sign-up page for lunch on January 7th, which allows us to keep registration costs low for you.

[https://www.eventbrite.com/e/2018-code4lib-midwest-conference-tickets-42889015199 Link to conference registration]

==Logistics==
====Getting Here/Parking====

Parking Information

Parking for visitors may or may not require a permit. See the information below for parking restrictions.

Permit Required

* At all times for University surface lots
* From 7 a.m. to 6 p.m., Monday through Friday, on Spring, Oak and Maple Streets

Visitors may purchase a permit at the Parking Office (128 Campus Avenue Building, 301 South Campus Ave) during business hours. Permits can also be purchased ahead of time online. The printed receipt serves as your permit, please be sure to print it out and place it on the driver’s side dashboard of the vehicle so it is visible to parking enforcement staff. The cost is $3 per day.

Permit Not Required

* Any parking meter. The cost is $1.00 per hour. Time limits at meters vary, so please read the display on the meter for details. Vehicles with parking permits must pay hourly rates at meters.
* Campus Avenue Garage ($1.00 first hour, $0.50 each additional hour)
* North Campus Garage ($1.50 first hour, $1.00 each additional hour)
A detailed map of Miami University Parking lots can be found here: http://miamioh.edu/_files/documents/parking/2017-18-parking-map.pdf.

* [http://www.miamioh.edu/parking/transportation/index.html Information on traveling to Miami University]

====Accommodations====
We do not have block reservations arranged at any of these hotels. Check the site's mapping feature, at least four of those listed are within walking distance of the King Library conference site.

* [https://www.enjoyoxford.org/lodging/ List of Lodging options from EnjoyOxford.com].

====Meals====
Coffee, tea, and pastries will be sponsored by Miami University Libraries on June 7th.
For all other meals check our list of local dining options on and around campus.
* [https://www.enjoyoxford.org/dining/ Dining in Oxford]

====Eat, Drink, Do Fun Things====
Working on a Google Map with a few dining suggestions near campus.

* [https://www.enjoyoxford.org/things-to-do/ Things to Do from EnjoyOxford.org]

====Wireless internet====
Miami University is a member of Eduroam, and public wireless is available on campus.

====Other Questions?====
Contact Craig Boman at bomanca@miamioh.edu

== Schedule ==

===== Outline of June 7 =====
Outline of June 7
Location: Advanced Inquiry Space (AIS), first floor King Library

8 am: Check-in and breakfast
9 am: Welcome and introductory remarks

9:30 am: Scott Williams - Recovering from a failing technology project: Williams will share experience at the Digital Public Library of America with confronting a troublesome project and how they were able move forward in a positive way for all staff members.

10 am: Break (Whiteboard breakout session ideas)

10:15 am: Peter Murray - Introducing FOLIO, A Platform of Services for Libraries: How nimble is your library automation system? What if your automation system resembled apps on a smartphone -- allowing you to choose apps that meet your needs with the expectation that they will sensibly communicate with each other? FOLIO is a library services platform -- infrastructure that allows cooperating library apps to share data. Librarians, developers, and user experience designers from all over the world are participating in designing and creating this open source effort. The FOLIO project is also an effort to build a sustainable, community-driven collaboration around the creation of a modern technology ecosystem that empowers libraries. Attendees will learn key aspects of the FOLIO project and how the FOLIO platform technology will impact library service offerings. Attendees will also learn how they can participate in the FOLIO community.

11:05 am: Announcements (Tally breakout session preference before lunch)

11:15 am-1 pm: Lunch in Oxford's uptown. (Lunch group sign up sheet).

1:00 am: Announcements

1:05 pm: Breakout sessions (various rooms in King Library)

2:15 am: Wesley Teal - Alma Enumerator: Experiments in Automating Tedium: What do you do when an ILS migration leaves a ton of your serials information behind? Well, you can fix thousands of item records by hand or you could use a little bit of Python and a lot of trial and error to automate your troubles away. This is the story of taking the second option and tribulations and triumphs involved. Alma Enumerator is a set of Python scripts that use the Alma API to parse free text item description fields and convert them enumeration and chronology data that can be uploaded back into Alma. The presentation will cover the problem that needed to be solved, the design considerations, complications encountered during development, and the highlights and shortcomings of the collection of scripts that became Alma Enumerator.

2:45 pm: Break

3 pm: Tammy Stitz - Making your PDFs universally accessible: One of the largest problems for students who use screen readers is reading PDFs. Even the intellectual content of their courses is easier to understand than trying to figure how to read the PDF. Sometimes PDFs cannot be read and other PDFs are read as blocks of text without an easy way to jump to different sections, which is problematic for long documents in particular. This presentation will discuss the features of an accessible PDFs based on the Web Content Accessibility Guidelines (WCAG) 2.0. It will show how to correct some issues using Adobe Acrobat DC when using a few different programs to generate the PDFs.

3:30 pm: Stephen Cassidy and Jason Michel - Building Discovery Layers: a Modern Approach: In this presentation we will discuss how the Ohio State University Libraries built a discovery layer utilizing existing vendor APIs like sierra and EDS, created custom APIs, and rendered results via the Vue javascript framework. We will discuss all layers of the project: Node.js, Elasticsearch, Vue.js, Lexicon (our custom built API environment), Drupal and more.

4 pm: Lightning talks and day closing announcements

5-7 pm: Dinner in Oxford's uptown

7-9 pm: Game night at King Library.
-join us for a game night at King library from 7-9p

===== Outline of June 8 =====
Location: Advanced Inquiry Space (AIS), first floor King Library

8-9 am: Breakfast

9 am: Choose Your Own Adventure: Choose format based on informal survey (voting day before) Hackathon, hands on session, networking, breakout session, lightning talks.

10:30 am: Break

10:45 am: Samuel Hansen - PodcastRE Not Podcatcher: Archiving Podcasts for Research: While there are many solutions to the problem of downloading and storing podcasts, none of them take into account the needs of archivists or researchers. This is only fair as most people, including myself on most days, are just downloading them for entertainment, but as podcasts increase in importance in culture so does the need for preserving them for both posterity and research. This is the goal of PodcastRE, http://podcastre.org, created by Jeremy Morris and Eric Hoyt at UW-Madison. During the evolution of the project which I have been a part of for the past year, from iTunes collection to full blown archive, many unexpected and interesting obstacles have reared up. In this talk I will discuss some of them, particularly the ways podcasts, and their RSS feeds, create challenges to those of us trying to store their contents long term, the new data model we had to create to deal with these challenges, and how we try to deal with the many changes creators can make to the RSS feeds at any given time.

11:15 am: Glen Horton - Mindful Coding: How does writing or reviewing code make you feel? Stressed? Fatigued? Anxious? Things like deadlines, project overload, and work environments can have a big impact on how developers feel when they interact with code. How can developers focus their attention, create better products, and increase their overall well-being all at the same time? Mindful coding. Mindfulness has been used to reduce stress and increase the quality of people's lives and it can be used during development as well. Glen will share the mindful approach he takes to writing and reviewing code at the University of Cincinnati Libraries. Learn how being present in the moment, focusing, and empathizing with users can lead to a better product and actually be therapeutic for the developer.

11:45 am: Wrap-up announcements / survey link

==Programming Sign-up==

Code4Lib Midwest programming depends on the folks attending the conference. Please consider giving a presentation or lightning talk, or submitting your ideas for a hackfest/breakout session.

Share what you are working on! Add your name and a description below. Please also let us know how long you'll need (10 or 20 minutes), and whether you prefer Wednesday or Thursday (or if it doesn't matter). Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. If you don't have a wiki account and don't want to sign up for one, please email [mailto:bomanca@miamioh.edu bomanca@miamioh.edu].

===Presentations ===

'''Title''' - Presenter, Affiliation

===Lightning Talks===

Have something cool to share but you don't want to be in front of the room for more than 5 minutes? Lightning talks are for you. 5 minute max. Sign up now or at the conference:

*'''Title - Presenter

===Breakout Sessions===

Actual breakout sessions presented and locations will be determined on June 7. Please propose an idea here if you are willing to facilitate a discussion on a topic.

'''Title'''

==Code of Conduct==
Code4Lib seeks to provide a welcoming, fun, and safe community and conference experience and ongoing community for everyone. We do not tolerate harassment in any form. Discriminatory language and imagery (including sexual) is not appropriate for any event venue, including talks, or any community channel such as the chatroom or mailing list.
Harassment is understood as any behavior that threatens another person or group, or produces an unsafe environment. It includes offensive verbal comments or non-verbal expressions related to gender, gender identity, gender expression, sexual orientation, disability, physical appearance, body size, race, age, religious beliefs, sexual or discriminatory images in public spaces (including online), deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
===CodeOfConduct4Lib===
[https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md Read and contribute to our full Code of Conduct document on GitHub]

2018 Code4Lib Midwest Meeting

2018-02-27T00:58:48Z

JerryYarnetsky: /* Getting Here/Parking */

2018 Code4Lib Midwest Meeting

2018-02-27T00:52:48Z

JerryYarnetsky: /* Logistics */

2018 Code4Lib Midwest Meeting

2018-02-27T00:52:16Z

JerryYarnetsky: /* Eat, Drink, Do Fun Things */

2018 Code4Lib Midwest Meeting

2018-02-27T00:51:04Z

JerryYarnetsky: /* Meals */

2018 Code4Lib Midwest Meeting

2018-02-27T00:49:56Z

JerryYarnetsky: /* Accommodations */

2018 Code4Lib Midwest Meeting

2018-02-27T00:48:52Z

JerryYarnetsky: /* Logistics */

2018 Code4Lib Midwest Meeting

2018-02-27T00:45:22Z

JerryYarnetsky: /* Meals */

2018 Code4Lib Midwest Meeting

2018-02-27T00:42:36Z

JerryYarnetsky: /* Travel */

2018 Code4Lib Midwest Meeting

2018-02-27T00:23:07Z

JerryYarnetsky: /* Accommodations */

2018 Code4Lib Midwest Meeting

2018-02-27T00:21:48Z

JerryYarnetsky: /* Accommodations */

2018 Code4Lib Midwest Meeting

2018-02-27T00:19:36Z

JerryYarnetsky: /* Accommodations */

2018 Code4Lib Midwest Meeting

2018-02-27T00:18:29Z

JerryYarnetsky: