The Code4Lib 2016 Philadelphia Committee is pleased to announce that we have finalized the dates and location of the 2016 conference.
The 2016 conference will be held from March 7 through March 10 in the Old City District of Philadelphia. This location puts conference attendees within easy walking distance of many of Philadelphia’s historical treasures, including Independence Hall, the Liberty Bell, the Constitution Center, and the house where Thomas Jefferson drafted the Declaration of Independence. Attendees will also be a very short distance from the Delaware River waterfront and will be a short walk from numerous excellent restaurants.
As we’ll be reserving almost all of the space within the hotel for our conference (both rooms and conference spaces), Code4Lib 2016 will have the tight-knit community feel we know is important.
More details to come soon; in the meantime, the Keynote Committee is gearing up to open submissions for the conference keynote speaker, so be sure to contact them at firstname.lastname@example.org for more information, or you can nominate a keynote speaker at http://wiki.code4lib.org/2016_Invited_Speakers_Nominations.
Also, our Sponsorship Committee is actively looking for sponsors for 2016, so please contact the committee via Shaun Ellis to learn about all the ways your organization can help sponsor our 2016 conference.
It’s shaping up to be a great conference this year, and there will be lots more opportunities to volunteer. Our team is looking forward to seeing you on March 7!
The Code4Lib 2016 Philadelphia Committee
Submitted by wtd on Thu, 2015-09-17 16:47
Creating Tomorrow’s Technologists: Contrasting Information Technology Curriculum in North American Library and Information Science Graduate Programs against Code4lib Job Listings by Monica Maceli recently appeared in the Journal of Education for Library and Information Science 56.3 (DOI:10.12783/issn.2328-2967/56/3/3). As the title states, it studies listings on jobs.code4lib.org:
This research study explores technology-related course offerings in ALA-accredited library and information science (LIS) graduate programs in North America. These data are juxtaposed against a text analysis of several thousand LIS-specific technology job listings from the Code4lib jobs website. Starting in 2003, as a popular library technology mailing list, Code4lib has since expanded to an annual conference in the United States and a job-posting website. The study found that database and web design/development topics continued to dominate course offerings with diverse sub-topics covered. Strong growth was noted in the area of user experience but a lack of related jobs for librarians was identified. Analysis of the job listings revealed common technology-centric librarian and non-librarian job titles, as well as frequently correlated requirements for technology skillsets relating to the popular foci of web design/development and metadata. Finally, this study presents a series of suggestions for LIS educators in order that they continue to keep curriculum aligned with current technology employment requirements.
Submitted by cbeer on Mon, 2015-07-27 17:38
Stanford University Libraries will host a Code4Lib Northern California regional meeting on Tuesday, August 4, 2015 in the Lathrop Library on Stanford's campus. We'll have a morning session with lightning talks about various topics and an afternoon of smaller breakout and working sessions.
You can get more details about the event and register on the Code4Lib NorCal wiki page.
Submitted by wtd on Wed, 2015-07-15 15:00
Code4Lib Journal issue number 29 has just been published. It has a broad range of articles that can be loosely grouped as follows:
Front End Features:
Review and Update of Previous Work:
Submitted by wtd on Wed, 2015-04-15 14:38
Submitted by wtd on Sat, 2015-03-07 23:40
Submitted by fxk on Sat, 2015-03-07 23:14
Submitted by wtd on Sat, 2015-02-21 21:00
The sixth Code4Lib North meeting will be on June 4--5, 2015 at the St. Catharines Public Library, 54 Church St., St. Catharines, Ontario. St. Catharines is on the Niagara Peninsula on the south side of Lake Ontario, close to the American cities of Buffalo and Rochester in New York. See the wiki page for details and to sign up for a talk.
Submitted by wtd on Sat, 2015-02-21 20:51
Code4Lib seeks to provide a welcoming, fun, and safe community and
conference experience as well as an 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
- Initial Incident
If you are being harassed, notice that someone else is being harassed,
or have any other concerns, and you feel comfortable speaking with
the offender, please inform the offender that he/she/ze has affected you
negatively. Oftentimes, the offending behavior is unintentional, and the
accidental offender and offended will resolve the incident by having
that initial discussion.
Code4Lib recognizes that there are many reasons speaking directly to
the offender may not be workable for you (including but not limited to
unfamiliarity with the conference or its participants, lack of spoons,
and concerns for personal safety). If you don't feel comfortable
speaking directly with the offender for any reason, skip straight to
If the offender insists that he/she/ze did not offend, if offender is
actively harassing you, or if direct engagement is not a good option
for you at this time, then you will need a third party to step in.
If you are at a conference or other event, find an event organizer or
staff person, who should be listed on the wiki.
If you can't find an event organizer, there will be other staff
available to help if the situation calls for immediate action.
If you are in the #code4lib IRC, the zoia command to list people
designated as channel helpers is @helpers. At most times, there is at least one helper in the channel.
For the listserv, you have a free-for-all for public messages; however,
the listserv does have a maintainer, Eric Lease Morgan.
- Wider community response to Incident:
If the incident doesn't pass the first step (discussion reveals offense
was unintentional, apologies said, public note or community is informed
of resolution), then there's not much the community can do at this point
since the incident was resolved without outside intervention.
If incident results in corrective action, the community should support
the decision made by the Help in Step 2 if they choose corrective action,
like ending a talk early or banning from the listserv, as well as
support those harmed by the incident, either publicly or privately
(whatever individuals are comfortable with).
If the Help in Step 2 run into issues implementing the CoC, then the
Help should come to the community with these issues and the community
should revise the CoC as they see fit.
In Real Life people will have opinions about how the CoC is enforced.
People will argue that a particular decision was unfair, and others will
say that it didn't go far enough. We can't stop people having
opinions, but what we could do is have constructive discussions
that lead to something tangible (affirmation of decision, change in CoC,
modify decision, etc,).
Participants asked to stop any harassing behavior are expected to comply
immediately. If a participant engages in harassing behavior, organizers may
take any action they deem appropriate, including warning the offender,
expulsion from the Code4Lib event, or banning the offender from a chatroom
or mailing list.
Specific sanctions may include but are not limited to:
- warning the harasser to cease their behavior and that any further reports
will result in other sanctions
- requiring that the harasser avoid any interaction with, and physical
proximity to, their victim for the remainder of the event
- early termination of a talk that violates the policy
- not publishing the video or slides of a talk that violated the policy
- not allowing a speaker who violated the policy to give (further) talks at
- immediately ending any event volunteer responsibilities and privileges the
harasser holds requiring that the harasser not volunteer for future Code4lib
events (either indefinitely or for a certain time period)
- requiring that the harasser immediately leave the event and not return
- banning the harasser from future events (either indefinitely or for a
certain time period)
- publishing an account of the harassment
Code4Lib event organizers can be identified by their name badges, and will
help participants contact hotel/venue security or local law enforcement,
provide escorts, or otherwise assist those experiencing harassment to feel
safe for the duration of the event. Code4Lib IRC volunteers can be identified
by issuing the
@helpers command to the #code4lib bot named "zoia".
If an incident occurs, please use the following contact information:
- Conference organizers: Tom Johnson, 360-961-7721 or Evviva Weinraub, 617-909-2913
- Hilton Portland & Executive Tower: 503-226-1611
- Portland Police Department: 503-823-0000
- Portland Women's Crisis Line (24/7): 503-235-5333 (or toll-free: 888-235-5333) 24/7
- Radio Cab: 503-227-1212
- IRC channel administrators: anarchivist, mistym, mjgiarlo, ruebot; or enter
@helpers in the IRC channel
We expect participants to follow these rules at all conference venues,
conference-related social events, community gatherings, and online communication channels.
We value your participation in the Code4Lib community, and your efforts to
keep Code4Lib a safe and friendly space for all participants!
Licensed under CC0
Based on the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers.