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

Code4Lib Conference Hosting

If you wish to host a Code4Lib Conference in your community, please review this information before applying. The Code4Lib Conference occurs in or near February each year, to provide a complement to the Access Conference.

Requirements of a Hosting Site

  • A host (usually a committee) willing to make local arrangements and coordinate with the site. Many colleges and universities have conference planning assistance.
  • An auditorium or similar space suitable for the conference itself (min 250), and room for four or more "breakout" groups (30-50), which may be a combination of the main space and smaller rooms. Note that while a keynote may be held in an auditorium, it is preferable for the main conference day to have tables and chairs for seating.
  • Wireless network available to attendees free or sponsored by the conference
  • A commitment to work with the conference planning group to help keep attendee costs to a minimum. Past costs have been about $120-160 including meals for 3 days. This requires substantial sponsorship from outside institutions and the hosting institution.

Additional Desirable Qualities

  • Small college or university town (why? "amenities", my friend, amenities). Conferences are also often held in large cities.
  • Reasonably near a major airport (we are prepared to interpret this liberally if the other qualifications are strong)
  • Some distance away from the last conference site, all things being equal (to spread the travel pain)
  • Pre-conference day/events, preferably with optional separate registration

What the Hosting Site is Responsible For

  • Since there is no legal Code4Lib entity, the hosting site must provide a fiscal sponsor for signing any necessary contracts for space or hotel rental. From a legal point of view, the sponsor is putting on the conference with Code4Lib branding. This institution is responsible for gathering sponsorship and registration funds and then transferring them to next year's host. The hosting site may choose to contract with other entities as necessary to fulfill these responsibilities.
  • Managing the program planning process (scheduling and arranging the presentation application and voting process, etc.) Prior years have used a voting mechanism tied to the Code4Lib website (e.g., this); the same system may be used for subsequent conferences.
  • Arranging evening networking opportunities (e.g., interesting and/or good restaurants and bars and/or events)
  • Leading the effort to sign on conference sponsors (various members of the community are expected to volunteer to help sign up sponsors

What the Conference Planning Groups are Responsible For

These items are the responsibility of the Code4Lib Conference planning group (anyone on the conference planning list, which is open to anyone), but the conference host is often actively involved with these aspects as well:

  • Participating in garnering conference sponsors
  • Assisting with conference planning tasks

See also: How to Plan a Code4LibCon and the wiki for various pages used for previous conferences

Results of the journal name vote

Here are the results of the code4lib journal name vote:

  1. /lib/dev: A Journal for Library Programmers (14 votes)
  2. Indexed: The Library Coder’s Quarterly (11 votes)
  3. Code4Lib Journal (8 votes)
  4. TIE: /dev/lib/journal and Access Points (7 votes each)

All other names received 5 or fewer votes. 28 people voted, four of whom voted for 5 or more names.

Thanks to everyone who participated!

#dspace

If you are a dspace user/admin/fan there is a new irc channel on freenode #dspace for discussing all things dspace.

Topic: 

Pages

Subscribe to code4lib RSS