2007 Conference Schedule Now Available

The 2007 Conference Schedule is now available. There may be some minor tweaks to be made still, but it is mostly set. It is an incredible line-up, plus there are a lot of cool unknowns hidden in the Lightning Talks and Breakout Sessions, for which ideas and sign-ups will be taken at the conference. See you there!

code4lib 2007 pre-conference workshop: Lucene, Solr, and your data

9am - 5pm, Tuesday February 27

Location Updated: Because of the overwhelming response, the pre-conference has been moved to the Tate Student Center, Room 137.

This will be a full day event devoted to lucene and solr.
The event will be led by Erik Hatcher, committer on the Lucene and Solr projects, and co-author of Lucene in Action, and Java Development with Ant.

The morning will be devoted to background and theory, and the afternoon will be an opportunity to try some hands-on projects. Participants should either bring a wi-fi enabled laptop or be prepared to look over someone else's shoulder. So that we can get as much accomplished in the workshop as possible, we will provide a list of software and documentation to be downloaded before the workshop. If you are interested in working with a specific data set, please bring the data set with you, preferably on a sharable media format (e.g., CDROM, USB Flash Drive) so that we can exchange data sets quickly and easily. To save time at the event, please get your data into XML before the conference.

There is no registration fee to attend the workshop. However, so that we can plan for adequate space, please register by emailing bess [at] virginia [dot] edu with a simple message that you plan to attend. Registration is full! Then remember to book your flight a day early and reserve an extra night in the hotel. Also, please join the mailing list for the pre-conference if you want to receive all the communication that will be sent out about it: http://groups.google.com/group/code4libpreconf

ADDED:
We have over sixty people, and more people are joining all the time. That is a lot of people to handle for a hands on workshop. In order to handle this, we're going to divide into teams based on what language you feel most comfortable using with solr. I'd also like to ask that a couple of people volunteer to be the coordinator of each team. If you're a coordinator, your job is to make sure you have downloaded all the software, you have a good data set to work with, and you've at least run through the tutorial and been able to get some data into solr. Also, you should probably be pretty comfortable with your chosen programming language. You can come here to sign up for a team, and indicate whether you'd be willing to act as a coordinator. The purpose of this is to make sure we know before the event whether we have enough coordinators for each language, and to make sure we don't spend all our time the day of the event trying to form groups.

Team Java:

  1. Martin Haye (coordinator)
  2. Ralph LeVan
  3. Emily Lynema
  4. Maureen Kelly
  5. Kevin Clarke
  6. Jerry Persons
  7. Tim Donohue
  8. Matt Cordial

Team XSLT / Cocoon:

  1. Bess Sadler (coordinator)
  2. Art Rhyno
  3. Jon Gorman
  4. Walter Lewis
  5. Ryan Steinberg

Team Ruby / Flare:

  1. Ross Singer (coordinator)
  2. Erik Hatcher (coordinator)
  3. Nathan Vack
  4. Mike Beccaria
  5. Eric Larson
  6. Steve Toub
  7. Tom Wood
  8. Andrew Nagy
  9. Hongbin Liu

Team Python:

  1. Gabriel Farrell (coordinator)
  2. Dan Chudnov
  3. Ed Summers
  4. Xiaoming Liu
  5. Bill Erickson (observer)
  6. Anjanette Young

Team PHP:

  1. Dan Scott (apologist)
  2. Jean Rainwater
  3. Jonathan Rochkind
  4. Tito Sierra
  5. Jonathan Blackburn
  6. Andrew Darby
  7. Jay Datema
  8. Antonio Barrera
  9. Parmit Chilana
  10. Karen Coombs

Team Perl:

  1. Wayne Schneider (will switch to PHP if there are no other perlers)
  2. Devon Smith
  3. Guoying (Grace) Liu
  4. Michael Doran
  5. Mike Rylander
  6. Kristina Long
  7. Mark Matienzo (the PHP defector)
  8. Michael Witt

Code4lib 2007 Presentation Runoff-vote

We had four presentations tied for the last two spots. This means we'll have a runoff vote for these two presentations. Voting will close around midnight Tuesday night/Wednesday morning EST. Everyone gets one vote, the two highest vote getters are in!

Here are the candidates:

Open-source software and the intellectual property disclosure process in academia

Michael Doran

This presentation will cover the copyright issues and pitfalls that arise when a locally created software application is being considered for release under an open-source license. It will be based on the knowledge and experience gained shepherding two applications through the intellectual property disclosure process at the University of Texas at Arlington, so that the applications could be officially released as open source.

barton data

In light of the change in the README file at MIT:

What happened to the data?
--------------------------

We are currently evaluating legal issues about ownership and licensing possibilities
and hope to be able to be back online with it soon. Wish us luck.

the torrent has been temporarily (hopefully) disabled. Thanks to MIT for continuing to investigate how to make large bibliographic data sets available to the general public.

Topic: 

MIT Catalog Data

The Simile folks made MARC, MODS and RDF versions of Barton (the MIT Library Catalog) available as a test data set.

To show code4lib's support for Simile and open-library-data we've set up some torrents for the data.

Please help us seed this data far and wide.

Topic: 

Code4Lib Downtime

The server on which code4lib.org lives will be moving this week. I haven't set up an exact time yet, but there will be some downtime as it is moved to a new host. It may be Monday afternoon or perhaps Wed. or Thurs. (I'm hoping for Mon. afternoon). Details, when known, will be posted here and on the mailing list and IRC channel.

Update: Looks like Wed. will be the day for server migration.

Call for Proposals





We are now accepting proposals for prepared talks for Code4lib 2007.

Code4lib 2007 is a loosely structured conference for library
technologists to commune, gather/create/share ideas and software, be
inspired, and forge collaborations. It is also an outgrowth of the
Access HackFest, wrapped into a conference-ish format. It is *the* event
for technologists building digital libraries and digital information
systems, tools, and software. Code4lib 2007 will be held from February
28 through March 2 in Athens, Georgia.

Prepared Talk Information

Prepared talks are 20 minutes, and must center on "tools" (some cool new
software, software library or integration platform), "specs" (how to get
the most out of some protocols, or proposals for new ones), or
"challenges" (One or more big problems we should collectively address).
We will evaluate proposals on criteria of usefulness, newness,
geekiness, and diversity of topics.

Prepared talk proposals of 75 words or less are being accepted for
review now. Please send your name, email address, and proposal to:
code4libcon@georgialibraries.org
.

We cannot accept every prepared talk proposal, but multiple lightning
talk sessions will provide everyone who wishes to present with ample
opportunity to show off. Lightning talks are 5-minute presentations that
any conference attendee can sign up to present.

The proposal deadline is November 30, 2006, and proposers will be
notified by December 15, 2006. Voting on the proposals will be public,
and held in a similar fashion to SXSW.

Code4Lib2006 Audio

The audio for the 2006 Code4Lib Conference is now available online. You can get it the following ways.

Please let me know if you have any problems. Unfortunately quite a few of the objects in Dspace had multiple mp3 files associated with it. It looks like some presentations were cut across cd's and it also seems that some use the same file. Atom 1.0 allows multiple enclosures, which is what I used so that it was associated with the same URI. Unfortunately most aggregators only support single enclosures (RSS only allows one depending on the interpretation) so you may only get the first part. Also the files are rather large. I'm hoping to go through and seperate the individual presentations and then post an updated feed. I still need to determine the copyrights of the audio however.

I created the Atom by hand and carried over the majority of the metadata. It's valid so you should be able to parse it for whatever you want.

book club

So a bunch of us in #code4lib are thinking of starting up a book club to read tech books together, learn from each other in the process, and hopefully use a bit of peer pressure to propel ourselves into actually finishing a book.

The first book we're proposing we read is Practical Common Lisp which is available in print and also online. Lisp and functional languages in general are enjoying a bit of a renaissance at the moment, so we figured this might be a good one to start with. It's also very, umm, practical--building working code to parse ID3 tags (metadata!) and the like.

Should we create a google group or something? Any suggested name for the group? Is there really any need to limit our membership to people in libraries? How about books4code?

Interested? Suggestions? Bueller? Feel free to tack comments on here.

Update: A Google Group and a wiki have been created.

Improving Code4LibCon 200*

There have been some posts in the blogosphere about things participants did not enjoy about the previous year's Code4Lib conference. Since planning has started for the 2007 conference, I thought now would be a good time to open the doors and ask what should be improved about the conference. What should be done the same and what should be done differently? Here is a place to start gathering voices...

Pages

Subscribe to code4lib RSS