Monthly Archives: September 2011

Thanks Ed Summers for referencing my post suggesting a microdata solution to ‘alternate format’ advertisement for citation harvesting. Ed’s basically arguing for simply using the ‘rel’ attribute on an <a> tag (with value ‘alternate’) instead. In my original post, I … Continue reading →

Proposal: A method of exposing alternate representations of entities embedded in HTML, using HTML5 microdata conventions. [This is just a draft for discussion — note the key URL begins http://example.org, and is just a placeholder, it should not be used in … Continue reading →

Many text indexes end up removing punctuation, and thus having trouble with retrieval of terms like “C++” and “C#”.  I think even Google used to back in the day, although these days Google seems to index just about all punctuation … Continue reading →

Phew, how’s that for a jargon-filled title. I have a Rails engine I help develop. It’s not suitable for new 3.1 “isolation”, it really does want to interact with the main app that’s hosting it, injecting behavior into it and … Continue reading →

A query for help in identifying what vendors are available for Koha support and/or hosting in the US. In the tricky situation of someone that already has a hosted Koha installation, but is unhappy with their current vendor, trying to … Continue reading →

I’m finding the discussion on the RDA listserv regarding ‘kits’ and RDA content/carrier/genre (ie, form/format) vocabularies to hit on some interesting pragmatic theoretical questions. I suggested in one post that the RDA-intended MARC 336, 337, 338 should not be considered … Continue reading →

From a thread on the RDA listserv, discussing how to enter the things we’ve called ‘kits’ under RDA.   The general consensus seemed to be that RDA supported entering the content/carrier/genre of each constituent part, but didn’t neccesarily support a … Continue reading →

LITA’s Information Technology and Libraries actually does have some interesting content in it. Here’s the latest issue.  Oh, but you probably can’t read it, unless you are a LITA member with a login. I suspect this has been a topic … Continue reading →

The new Google Books API, just like the old, recommends you send the actual client IP address using an X-forwarded-for header.  If your server that’s making the requests is running on an internal NAT’d network, like many academic institutions, then … Continue reading →

So there’s an LCSH heading “C# (Computer program language)” In some of my MARC records, it is encoded just like that, with an ascii number sign, byte 23. In other of my MARC records, it is instead encoded as “U+266F … Continue reading →