Over the last couple of years, I’ve been working on-and-off on improving the Database of Early Chesapeake Architecture. I’d recently gotten the data (again) from Swem Library and had been working on pushing it to a more open framework (it was ColdFusion + MSSQL; now Rails + Postgresql). What I wanted to be able to add in is an extensible method of citation for the various buildings and sites used (check out the work-in-progress). At the time, I tried to use RefWorks (with very little success) to handle the citations, but with the improvements to Zotero (and it’s Group ability), I thought I’d go down this road and test if this is a viable method of citation management.

I first took a look at Jeremy’s phpZotero code. The first thing I noticed is that there’s a pretty funky way that you have to construct URLs for the “API” (I think the Zotero API is more of an RSS decorator than an API, but hopefully they’re working on that). Essentially you construct a URL requests to the Zotero API server with a user ID. Unfortunately, most people don’t know their user_id, so the PHP code goes and looks this up on a different server, parses out the user_id, then constructs an HTTP request for RSS data from the API server. I kind of brace a bit at the thought of every request needing to go to two servers (multiple points of failure, speed, etc.). When I started creating a ruby wrapper for these calls, I made the object use the user_id (Integer) and not the user_name (String). Knowing folks might not know their user_id, I whipped up a quick Sinatra app on heroku to look up Zotero User ids: zotero-id-finder (source on github).

Next, I needed something to not have to use Nokogiri all the time to grab info off the Zotero server. I made a basic Gem to wrap these requests named rzotero. This is really helpful, but what I really wanted to do is add citations to ActiveRecord models a la acts_as_taggable. To that end, I started mocking up acts_as_citable which will allow you to add in citations identifiers to be used with rzotero plugin to record and display items in a collection in ActiveRecord contexts.

As a warning, all of these are in a pre-alpha-ish state and may (badly) break your code (especially since it’s lightly tested right now). As things progress, I’ll have more posts here, and over on the Scholars’ Lab site.

To me, it is one of the most import and useful tools any scholar can posses. My one gripe with it was that if you were working on something on a computer at say, work, and then went home to do more work, there wasn’t a great way to syncrhonize everything. I resourced to portable Firefox on a USB stick which worked reasonably well. Now, with the 1.5 Synch preview, I don’t need that any more. I can even synch it up to my server (I set up my own WebDAV and store my docs on that system).

Needless to say, I’m a huge fan. It’s not quite FOSS (which would just top this off), but it’s pretty close. Shoot, I even recently got a questionnaire about Zotero use for an article from a Law student.

Anyway, the point of all of this rambling is to set up my absolute disgust when I read Reuters (makers of End Note) are suing George Mason for Zotero for $10,000,000. It seems Zotero’s ability to convert its proprietary “ens” format into Zotero violates its copyright.

Hopefully they won’t sue the Vufind project for allowing people to download references into End Note. Shoot, at this point, I’m ready to make it not a feature on principal…