You are here

conferences

You know, when people get together and talk about stuff.

Code4Lib 2015

Code4Lib 2015 will be held at the Hilton Portland & Executive Tower in downtown Portland, OR on Februrary 9 - 12, 2015.

Pre-conferences will be held Monday February 9, and the main conference on February 10 - 12.

Participate in the planning process by signing up for Conference Committees.

Preconference Proposals

We are now accepting pre-conference workshop proposals for the 2015
Code4Lib in Portland, Oregon. These workshops can either be a 1-day or a
1/2-day session and will occur on Monday, February 9, 2015.

To propose a session, please add your proposal to the wiki page directly,
following the proposal formatting guidelines.

Keynote Proposals

All nominees have been contacted and the 19 (!) nominees included in this election are all potentially available to speak. The top two available vote recipients will be invited to be our keynote speakers this year. Community voting ended on Tuesday, November 18th, 2014.

Presentation Proposals

The Code4Lib 2015 Program Committee is happy to announce that voting is now open for prepared talks.

Voting will end on Tuesday, November 25, 2014 at 11:59:59 PM PT (GMT-8).

To vote, visit http://vote.code4lib.org/election/33, review the proposals, and assign points to those presentations you would like to see on the program this year.

Code4Lib NorCal 28 July in San Mateo

A one-day Code4Lib NorCal Meeting will be held 10am - 3:00pm on 28 July at 777 Mariner's Island Blvd., San Mateo (the building that the OCLC Research San Mateo office is in).

There is no cost, and OCLC will provide attendees lunch. Parking is plentiful and free.

Please see More information on the wiki.

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

Conflict Resolution

1. Initial Incident

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please inform the offender that he/she 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.

2. Escalation

If the offender insists that he/she did not offend, or if offender is actively harassing you, then you will need a third party to step in.

If you are at a conference or other event, find the event organizer or staff person. For #c4l14, that would be Tim McGeary. If you can't find the event organizer, please notify the CONCENTRA staff at the Registration Desk to help if the situation calls for immediate action.

If you are logged into the #code4lib IRC channel, the command @helpers can be entered which will cause the zoia robot to list people designated as channel helpers. There should be at least one helper in the channel most times.

For the listserv, you have a free-for-all for public messages; however, the listserv does have a maintainer, Eric Lease Morgan.

3. 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 really can't stop people having opinions, but what we could do here is have constructive discussions that lead to something tangible (affirmation of decision, change in CoC, modify decision, etc,), instead of reproducing the comments section of a story on a news site.

Sanctions

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 the event
* 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 in the #code4lib IRC channel (see above).

If an incident occurs, please use the following contact information:

* ** Conference organizers: Conference organizers are recognizable by a marking on their nametag; CONCENTRA Staff will be at the Registration Desk; and Tim McGeary, Chair of the Conference Committee.
* ** Sheraton Raleigh Hotel: 888-974-3068
* ** Raleigh Police Department: Emergency, 911 ; Non-emergency but response needed: 919-831-6311
* ** Sexual Assault Crisis Line (24/hr, by Interact): 866-291-0853
* ** TaxiTaxi: 1-919-333-3333 [Also the TaxiMagic smartphone app]
* ** IRC channel helpers: 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!

* Based on the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers.*

Code4Lib 2015 Call for Host Proposals

The Code4Lib Community is calling for proposals to host the tenth annual Code4Lib Conference in 2015. Prior to submitting a proposal we recommend reviewing the conference hosting web page and How To Plan a Code4LibCon on the wiki to learn more about the kind of venue the community seeks and the responsibilities involved with hosting the conference.

The deadline for proposals is midnight PST Wednesday March 12th, 2014. The decision will be made by a popular vote. Voting will begin on or around Friday March 14th, 2014 and will continue until midnight PST March 26th, 2014. The results of the vote will be announced Thursday morning at the Code4Lib conference 2014 and emailed out to the listserv.

You can apply by making your pitch to the Code4Lib Conference Planning list at code4libcon@googlegroups.com and linking to your proposal on the 2015 Hosting Proposals wiki page; attention to the criteria listed on the conference hosting page is appreciated. Good luck!

-----------------------------------------------------------
Have a look at past proposals for ideas:

2014 Winner:
https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw

2013 Winner:
http://tigger.uic.edu/~kayiwa/code4lib.html

2012 Winner:
https://sites.google.com/site/code4lib2012seattle

Code4Lib 2014 Sponsors

Code4Lib 2014 could not be successful without the generous support of our sponsors. We are very thankful to all of our sponsors for helping to defray the costs of the conference and supporting the scholarships we are able to provide to worthy recipients.

Platinum Sponsor:
OCLC
OCLC

Gold Sponsors:
Blacklight; Digital Library Federation; LucidWorks; Oregon State University Library; Penn State University
Blacklight
DLF
LucidWorks
Oregon State
Penn State

Silver Sponsors:
Ebsco; IndexData; Innovative Interfaces, Inc.; Microsoft Research; University of Pennsylvania Library

Bronze Sponsors:
Kuali OLE; Nashville Public Library; Princeton University Library; Proquest; UC-San Diego Library

Contributor Sponsors:
The Cherry Hill Company; DuraSpace; GitHub; User Friendly Consulting, Inc. (UFC, INC.)

Reception Sponsor:
North Carolina State University

Give-away Sponsors:
O'Reilly Media, Inc. is providing a free e-book for all Code4Lib 2014 attendees. You will receive your free coupon with your registration.

Rosenfeld Media is providing 20% off all books at http://www.rosenfeldmedia.com to all Code4Lib 2014 attendees, as well as providing books we will raffle off during the conference.

Table Sponsors
This year, we introduced a new table sponsorship opportunity for Projects, Non-Profit Organization, and Corporate Vendors to participate at Code4Lib 2014. We encourage you to visit our Table Sponsors before and after the general sessions, during the breaks, and after lunch to speak with them about their products, services, and projects. The following descriptions have been provided by the Table Sponsors (listed in alphabetical order):

Blacklight
Blacklight is a Ruby on Rails open source discovery platform. We’ll be available to help getting started with Blacklight, answering questions about the project, providing advice on configuration and customization, and demonstrating core Blacklight functionality and Blacklight-based applications, including the new digital collection and curation environment.

DuraSpace
Find out how to contribute to DuraSpace projects–DSpace, Fedora and VIVO–at the DuraSpace demo table.
The DuraSpace organization stewards three significant open source technology projects that provide long-term, durable access to, management and discovery of digital assets for more than 1,800 repository instances worldwide. Carol Minton Morris, DuraSpace, will be on hand to discuss DuraSpace services for open source projects and how you can get involved.
• The Fedora Project Fedora 4 team members will be available to discuss the latest Fedora 4 feature set designed to refresh and enhance Fedora's proven architecture, and offer demonstrations.
• The DSpace Project Tim Donohue, technical lead for the DSpace project, will be on hand to talk about DSpace development and demonstrate DSpace 4 (via the new vagrant-dspace development environment)
• The VIVO Project Learn about what's ahead for this groundbreaking network that facilitates scholarly discovery around the world through an open source semantic web application.

Ebsco
EBSCO Information Services provides a complete and optimized research solution comprised of research databases, e-books and e-journals—all combined with the most powerful discovery service and management resources to support the information and collection development needs of libraries and other institutions and to maximize the search experience for researchers and other end users. EBSCO provides robust APIs to our products, supports open projects such as Blacklight and VuFind, innovates its own API to benefit customers and partners with libraries to bring specific projects to fruition. EBSCO serves the content needs of all researchers whether they access EBSCO resources via academic institutions, schools, public libraries, hospitals and medical institutions, corporations, associations, government institutions, etc. For more information, visit the EBSCO Web site at: www.ebsco.com. EBSCO is a division of EBSCO Industries Inc., one of the largest privately held companies in the United States.

Innovative Interfaces, Inc.
Innovative creates cutting-edge products that allow libraries to succeed in a modern technology environment. The company’s market-leading solutions include: the Sierra Services Platform, the Millennium ILS, the Encore Synergy discovery application, Electronic Resource Management, and INN-Reach resource sharing. Innovative connects with thousands of libraries of all types in over 50 countries.

LucidWorks
LucidWorks, the trusted name in Search, Discovery and Analytics, transforms the way people access information to enable data-driven decisions. Leveraging technology built on Apache Lucene/Solr open source search, LucidWorks delivers unmatched stability, scalability, and time-to-delivery for search applications. LucidWorks Search provides ease of use development to access documents with sub-second query and faceting response time. LucidWorks tightly integrates Apache projects to build and deploy applications providing ubiquitous access to data trapped inside Hadoop.

Microsoft Research
Windows Azure for Research is an initiative from Microsoft Research to facilitate and accelerate scholarly and scientific research by enabling researchers to use the power of Windows Azure to perform big data computations in the cloud. Stop by and learn about our free training events and how cloud computing is being used for repositories, digital preservation and research data discovery and exploration.

Proquest
ProQuest® connects people with vetted, reliable information. Key to serious research, the company’s products are a gateway to the world’s knowledge including dissertations, governmental and cultural archives, news, historical collections, and ebooks. ProQuest technologies serve users across the critical points in research, helping them discover, access, share, create, and manage information.

The company’s cloud-based technologies offer flexible solutions for librarians, students, and researchers through the ProQuest®, Bowker®, Dialog®, EBL® ebrary®, and Serials Solutions® businesses – and notable research tools such as the Summon® discovery service, RefWorks Flow™, Pivot™, and Intota®, a new library services platform.

University of Pennsylvania Libraries
The University of Pennsylvania Libraries hosts several projects that might be of interest to the code4lib community. We welcome interest, and opportunities for collaboration and partnership around our development efforts, or opportunities to participate and contribute to similar efforts. Community-source and open-source are strategic for the Penn Libraries in our pursuit to reclaim control and direction of our services, and to participate in the redefinition of the academic library. In support of these strategic goals, the Penn Libraries has developed and partner in:
• DLA-Discovery – SOLR-based discovery that bridges library collections, and supports generalized discovery services for non-Library data
• DLA-Account Services – django-based portal for all transactional interactions with library users including traditional ILS functions, ILL & expedited borrowing, coursesite requests, document delivery, course reserves, and others
• Kuali OLE – next generation library management system built by and for academic libraries
• MetriDoc – building insight into our users, our process, and our collections
• PennVIVO – supporting collaborative researcher networking and exposing Penn’s contribution to scholarly inquiry

User Friendly Consulting, INC. (UFC, INC.)
UFC provides comprehensive document capture and forms processing solutions to meet all of the needs for your library. Our product line includes the full suite of products from ABBYY USA including FineReader Corporate, Recognition Server, and Flexicapture. Recognition Server is recognized as the industry-leading tool for capturing and providing OCR for libraries around the world. It is available with an easy to use API set that provides the means needed to connect it to legacy systems in your organization. Flexicapture takes the Recognition Server OCR engine and adds a high-volume, scalable document processing system in order to capture handwriting, checkmarks, and tabular data. Whether you need to automatically OCR and index documents by barcode, extract line items from a student transcript, or provide an enterprise wide document capture system Flexicapture is ready. In addition to the ABBYY suite, UFC also provides Quillix capture, an enterprise level web-based system that leverages the ABBYY OCR and Flexicapture engines while providing an extensible architecture built in .NET. A variety of quick-start packages are available for any of the solutions offered by UFC who strives to provide the highest level of customer service and consulting to make your organization succeed.

2014 Conference Schedule

Schedule for the 2014 Code4Lib Conference in Raleigh, NC.

Pre-conference Program

Monday, March 24

Pre-Conference day overview:

08:00-09:00 - Registration
09:00-12:00 - Morning sessions
12:00-13:30 - Lunch (on your own)
13:30-16:30 - Afternoon sessions
TBA - Evening session
18:00ish-20:00 - Newcomer Dinner
Detailed pre-conference schedule with meeting rooms
Preconference Descriptions

Conference Program

Tuesday, March 25

Wednesday, March 26

Thursday, March 27

All Tiled Up

Mike Graves, MIT Libraries

You've got maps. You even scanned and georeferenced them. Now what? Running a full GIS stack can be expensive, and overkill in some cases. The good news is that you have a lot more options now than you did just a few years ago. I'd like to present some lighter weight solutions to making georeferenced images available on the Web.

This talk will provide an introduction to MBTiles. I'll go over what they are, how you create them, how you use them and why you would use them.

Lucene's Latest (for Libraries)

Erik Hatcher, LucidWorks

Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc. The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability. This talk will distill and showcase the most relevant(!) advancements to date.

Under the Hood of Hadoop Processing at OCLC Research

Roy Tennant, OCLC Research

Apache Hadoop is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.

Queue Programming -- how using job queues can make the Library coding world a better place

Birkin James Diana, Brown University

In 2007 we built a system that dumped certain user web-requests for books into a database for offline-processing triggered via cron. We wanted to make the magic happen live, but knew it would take too long. Thus we created, sort of accidentally, a kind of old-fashioned static procedural job queue.

Over the years we we've been repeatedly impressed with how useful and robust this unintended architecture has been, and it fostered thinking about using real job queues in Library workflows.

Fast-forward to the present. We now are using _real_ job queueing, in production, for parts of the functioning of Brown Digital Repository. We've also used it for ingestion scripts, and plan to move more lots more code to this architecture.

I'd like to share & show:

  • our lightweight rq/redis job queueing setup
  • how using job queues can speed up workflows via using multiple workers
  • how job queueing can make workflows more robust, especially by simplifying failure handling
  • a way we've smoothly avoided race-conditions that can occur in concurrent-programming
  • a technique for using task-processing job queues to simplify complex workflows

rq: http://python-rq.org
redis (python): https://pypi.python.org/pypi/redis/

Pages

Subscribe to RSS - conferences