2018 Code4Lib Midwest Meeting

From Code4Lib
Revision as of 14:13, 24 January 2018 by CraigBoman (Talk | contribs) (initial posting)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


King Library

Miami University of Ohio

Google Maps


Registration link will be posted by the end of January.



There are airport shuttles to Oxford from either Dayton or Cincinnati airports.

More information on travel to campus


Hampton Inn Oxford, OH This newly constructed hotel near near campus, and within walking distance. We do not have a room block.

Wireless internet

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


We are attempting to find a sponsor for breakfast on June 7. Lunch and dinner will be local dinearounds.

Getting There/Parking

You are highly encouraged to take public transportation if possible; but getting to Miami may be easiest by car. Parking and transit information

Eat, Drink, Do Fun Things

Working on a Google Map with a few dining suggestions near campus

Other Questions?

Contact Craig Boman at bomanca@miamioh.edu


June 7, 9a-5p June 8, 9a-12p

Detailed schedule, June 7 & 8

Detailed Schedule (subject to change during the day)

Outline of June 7

8:30-9:00: Check-in and breakfast

9:00-9:15: Welcome and introductory remarks

9:15-10:15: Introductions / Successes / Struggles
One of the strengths of Code4Lib is our willingness to share experience and learn from each other. As an experiment, we will go around the room. Introduce yourself and give an example of (1) something you are proud of and (2) something you are struggling with. We hope that this will stimulate ideas for breakout topics and informal conversations.

10:15-10:30: Break

10:00-11:30 Lightning Talks/presentations

11:30-1:00 Lunch (Sign up)

1:00-2:30 Presentations/ Breakouts (4) (post-breakout lightning talks to report back)

3:00-3:15 Break

3:15-4:30 Presentations

Time TBD (~5PM-~8PM): Meetup at [http:// TBD] This bar is an easy bus ride from campus, and near many great dining options.

Outline of June 8

8:30-9:00: Check-in

9:00-10:30 Presentations and/or lightning talks

10:30-10:45 Break

11:00-12:00 Wrap-up |

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 bomanca@miamioh.edu.


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.


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.


Read and contribute to our full Code of Conduct document on GitHub