This file (vim.tgz) contains my .vimrc, my .vim folder (containing the rails.vim, project.vim, minibufexpl.vim, and other plugins), .screenrc and split screen file. Notes:
My .vimrc file is set up for the following:
To close a buffer, use :BD, not :q. The latter does not account for window layout.
Ctrl-h,j,k,l is mapped to switch windows. Normally you'd hit Ctrl-w followed by h,j,k,l.
To avoid having to save a file every time you switch a buffer, autowrite is enabled, meaning a file is saved when you move away from it.
F12 toggles the project window, F8 toggles the tag window.
Ctags is expected for taglist.vim. Uninstall as needed.
Using .screenrc and .screenrc.split: None of this needs to be changed much, and tutorials on Gnu screen are ubiquitous on the web. .screenrc.split shows how to start your server, split the screen, tail the development log, and start vim. To use, call screen -c ~/.screenrc.split in your rails directory.
When you open a file from the minibuf area or the project area, the file will open in the last window used. This can really screw things up if you've moved from tags to project, etc. This is the major weakness of vim as an IDE, but you can be more aware of where you move.
The rails.vim plugin is only activated if you open a file in a rails application.
You may want to update all of the plugins. Ruby and rails syntax files can be updated with 'sudo gem install vim-ruby --remote'.
Web Archiving Service - Mike Wooldridge, California Digital Library
Work is beginning to transform the eloquent yet arcane texts called
"library cataloging records" into data elements that will play well in
the Web. Beginning with the upcoming revised cataloging rules, called
Resource Description and Access, a team of researchers is exploring the
abstract model behind bibliographic description. Coyle will cover the
philosophy behind the project and will discuss current progress and
goals, as well as fears, risks, and even some confusion.
Anyone can propose a breakout session - please think about whether you would want a session to be held on Tuesday or Wednesday, depending on the order of talks and who you hope will attend. There are at least five rooms available each day, including the large meeting room, and we will route different proposed sessions to the different rooms depending on a quick show-of-hands survey just before each one begins.
This page will list any sessions proposed before the conference itself, but there will also be flip charts outside the meeting room where more sessions can be proposed.
Breakout Sessions 1 (Tuesday 14:40-16:00)
WorldCat Grid Services (for example, the WorldCat API) (Don Hamparian)
Traditionally (if two years can be called tradition) we hold a contest to pick the design for the front of the conference t-shirt. This year we did not receive many entries - in fact, we only had one official entry. Fortunately, it rocks (at least, I think so):
Jeremy Kemp - SJSU SLIS Dr. Jonathon Richter - University of Oregon
Second Life is web-enabled via XML-RPC and HTTP so that it can automatically export data out from
scripted 3D objects and import in from Web databases. Its hackability is under-reported in favor of tales about naked avatars and case studies of failed ad campaigns but we think this platform may be useful for hybrid 3D modules for ILS systems. Two mashup projects will be interesting to library coders:
Sloodle.org connects Moodle to 3D learning tools
the Salamander project is organizing a 3D learning objects taxonomy related to Merlot.org (http://tinyurl.com/2pvqp9).
The two founders will describe their projects and give tips for hacking SL.
We've recently hacked an API for the NYPL Digital Gallery to share images with the video collaboration platform, Kaltura. This could be your library's dream, or nightmare, depending where you sit. Is there a sweet spot between offering lightweight APIs - with possibly limited reliability - vs. trying to develop a bullet-proof API? Is the possible solution to seed the API to interested parties through feeds, with the implied expectation that it's a work in progress?
Corey A. Harper - Metadata Services Librarian, New York University
This talk proposes to introduce the DCMI/RDA task group, formed to analyze the relationship of RDA to other metadata communities and to examine the modeling of library metadata. Recent DCMI developments will be discussed, including the DC Abstract Model, Application Profiles, RDF declarations of metadata element sets and value vocabularies, the Singapore Framework, and the emerging concept of description set profiling. It is hoped that this will help to foster collaboration between code4lib and DCMI.