I’ve made a five-minute screencast explaining how publishers can join the newly-announced LibraryThing for Publishers.
Email tim@librarything.com with questions.
I’ve made a five-minute screencast explaining how publishers can join the newly-announced LibraryThing for Publishers.
Email tim@librarything.com with questions.
Labels: LibraryThing for Publishers, new feature, new features
See the main blog. (Posted to the wrong blog and too many links to this to just delete it.)
Labels: book covers, new feature
Tim and I will be at the American Library Association’s annual conference this year. We have new, new LTFL features to show off. You can find us at booth 2857 in the exhibit hall.
1. New features! We’ll be demoing our new catalog enhancers – never before seen by librarians. We’ll post an announcement all about the new features in a day or two.
2. An art installation! Yeah, you’ll just have to wait and see it. I can’t even describe it, other than to say that it takes away ennui.
3. More rhinos! Tim and I are both flying to Chicago with an inflatable rhino in our luggage. We plan on playing “Toss the Rhino”, and perhaps if we are feeling extra daring, “Pass the Rhinos“.
(Thanks to Brixton for the masticating rhino photo. The rhino tossing one’s mine. That’s Tim and Casey putting some English on the rhino.)
Labels: Tim, librarything for libraries, ltfl, new feature, new features, rhinos
We’ve added a new feature to the LibraryThing for Libraries Reviews Enhancement: the ability to categorize reviews for the blog widget.
Thus far, library patrons have been able to write reviews and rate books in their library’s catalog, add their reviews to their Facebook page and even create a widget that lets them show off their reviews on blogs and websites.
Now, libraries can show off reviews written by their patrons for specific library programs. Patrons and librarians can add categories to a review. The library can then create blog widgets with said categories – keep track of reviews for the Summer Reading Program, One Book, One City and book discussion groups.
This should be helpful all year round, but the inspiration for the feature came from a librarian’s request to manage the reviews children were going to be writing for the summer reading program at their library. They wanted some way to display the reviews separately from the rest of the reviews coming in.
Anyone who’s bought the Reviews Enhancement can use this feature starting immediately. Read here for instructions how to add and use it.
If you’d like more information about LTFL, and the enhancements that can take your OPAC from Library 1.0 to Library 2.0 overnight, fill out the interest form on the LTFL page.
The Reviews Enhancement isn’t available for all OPACs – currently, it supports Horizon, iBistro, iLink, eLibrary, Webvoyage, Voyager 7, WebPac, WebPac Pro and Koha. More are coming soon!
Labels: LTFL Reviews, categories, librarything for libraries, ltfl, new feature
LibraryThing for Libraries now has stats! Libraries in the program can see just where LibraryThing for Libraries is working for them, and where it’s not. You can evaluate changes, and justify it to your bosses.
We certainly suspect that LibraryThing enhancements are getting a lot more play than some other browse links—like LCSH subjects—or those of our competitors’, who put their enhancements on external pages. Indeed, we’re wondering if libraries would like to use LTFL’s stats structure to track other links too?
LibraryThing for Libraries Email List. We’ve set up a Google Group for LibraryThing for Libraries customers. We hope member libraries will join up. We’ve sent out invites to all the primary contacts.
Sign up to have your voice heard. We will be talking about the future of LTFL and where it should go.
Labels: librarything for libraries, ltfl, new feature, stats
A smart young programmer from a book-related company and I were talking. It turns out that, to validate ISBNs and get back both 10- and 13-digit versions he was submitting ISBNs to Amazon Web Services. That’s like calling NORAD to find out if it’s raining.* Nor did he seem likely to hunt around for an ISBN library for Ruby. After all, what he was doing worked.
So I made a quick, very stupid API, ie. http://www.librarything.com/isbncheck.php?isbn=0765344629
Don’t hit it more than 10 times/second. Otherwise, there are no usage restrictions.
Labels: apis, new feature
Shameless cross-post from the main blog, but I want all my Lib 2.0 chums to come and join the new Secret Santa system, SantaThing, I cooked up last night. Secret Santa for booklovers. Can you resist?
Labels: new feature, santathing, secret santas
Tagmash: alcohol, history gets over the fact that almost nobody tags things history of alcohol
Short version: I’ve just gone live with a new feature called “tagmash,” pages for the intersections of tags. This is a fairly obvious thing to do, but it isn’t trivial in context. In getting past words or short phrases, tagmash closes some of the gap between tagging and professional subject classifications.
For example, there is no good tag for “France during WWII.” Most people just don’t tag that verbosely. Tagmash allows for a page combining the two: France, wwii. If you want to skip the novels, you can do france, wwii, -fiction. The results are remarkably good.
Tagmash pages are created when a user asks for the combination, but unlike a “search” they persist, and show up elsewhere. For example, the tagmash for France, Germany shows France, wwii as a partial overlap, alongside others. Related tagmashes now also show up on select tag and library subject pages, as a third system for browsing the limitless world of books.
Booooring? Go ahead and play a bit:
That’s the short version. But stop here and you’ll never know what Zombie Listmania is!
Long version. LibraryThing has shown some of the things that book tags are good for, such as plain language, genre fiction, capturing identity and perspective, academic schools, staying current and changing over time. (Details and examples in footnote.*)
It also demonstrates some of the weaknesses, including:
As I’ve argued elsewhere and in my Library of Congress talk, problems 1, 2 and 3 are mitigated by having LOTS of tags. Idiocy, malice and personal junk fall out statistically. A tag here or there can’t be trusted, but a large body of tags in agreement is different.
Problems 4 and 5 are harder to tackle. Flickr has shown the way with one solution, statistical clustering. The screen shot below shows this–clusters of images related to the tag “bow.”

Some day–when I become a better programer?–I’m going to try this on LibraryThing data. It will help with ambiguity—the secondary tags on the various meanings of “leather” are surely wildly divergent! But I suspect it separates better than it clarifies. Flickr supposes that tags fall into discrete clusters, but subjects interact with books in extremely complex ways. On a more basic level, I am suspicious of the too-quick resort to algorithms against user data.*** After all, if computers are so good at figuring out meaning, why were users necessary in the first place? It smacks of technological revanchism.
So, where Flickr’s clusters are automated, tagmash is a semi-automated process. LibraryThing does the statistics, but users decide what the meaningful clusters are. Some mashes are interesting and useful. Some aren’t. By and large, uninteresting clusters won’t last.****
This certainly helps with ambiguity. Take the problemmatic tag leather, which divides easily into tagmashes like:
Now let’s take the “focusing” power of hierarchy. As mentioned above, there is no good way to get at “france during wwii.” The tag Vichy covers some of the ground, but not enough. Tagmash provides an answer.
The book list is good, and a simple union gets around an imposed hierarchy. Looking at the related LCSHs, for example, one is left in doubt whether France is part of World War II, or World War II part of France—or what:
Of course, both trees are equally artificial. David Weinberger writes how, in the real world, a leaf can be on many branches. But it’s equally true that what’s trunk and what’s branch are largely about where you start–dirt or pinecone. Either way, branching happens. The order of the branches isn’t necessarily important.
Even as it borrows some of the virtues of subject classification, tagmash keeps the strenghts of tagging. Subject systems are pre-built things. Now and then they get larger, but it takes deliberation and effort. What gets “blessed” is often surprising. I would have never predicted the unusually staid LCSH would have embraced:
But tagging has no limits. Think of the tagmash “erotica” and “zombies” and there it is. (Tagmash: erotica, zombies). Want to know what chick lit takes place in Greece? (Tagmash: chick lit, greece.) Young adult books involving horses? (Tagmash: horses, young adult.) Poems from or about San Francisco? (Tagmash: poetry, san francisco). Slavery in Brazil? (Tagmash: brasil, slavery.) Non-fiction books about Narnia? (Tagmash: narnia, -fiction.) The options are endless.
Of course, tagmash only narrows the gap. It doesn’t eliminate it. Tagmash: poetry, San Francisco still can’t distinguish between poetry about and poetry from San Francisco–it involves whatever is tagged “San Francisco” and that’s probably a mixed bag.***** Well-planned and carefully executed subject systems have strengths that no ad hoc, regular-person system can match.
Lastly—let there be no doubt—tagmash needs a very large quantity of tags to work. For tagmash after tagmash, the data is simply insufficient.
You’ve made it to Zombie Listmania! There are some obvious directions this can go:
Amazon calls its static, or dead, lists “Listmania.” All these tend to create a “Zombie Listmania,” lists of books that “won’t stay dead.” Instead, they change over time, as the underlying social and non-social data change. There’s no reason you couldn’t create “Zombie” versions of formal subject headings—a series of tags and other markers which approximated the content of a professionally-assigned subject heading.
Pretty cool idea, I think. We’ll see what we can do about it.
Details.
*What’s good about tagging:
**I’ve left out one problem, not covered at the LC—how “democratic” weighting can put Angela’s Ashes at the top of the Ireland tag. books. I want to write a blog post on the topic sometime. I think there are ways around it, and algorithmic solutions that nobody has really tried.
Aside: Much LIS anti-tagging polemic focuses on the most trivial of problems—spelling mistakes and “incorrect” tags. The former underestimates technology, the latter insults our intelligence. LibraryThing has dealt with the spelling problem, and has seen very few “wrong” tags. In fact, there are some serious problems with tagging. But you have to understand tags before you can see the problems, and many refuse to get past the idea that people will spell “white” wrong, or tag white horses as black.
***This is half formed. I have a problem with the reflexive “turn” from people-centered data to algorithms. I see this pattern again and again in software. Something transformative happens–something human. But it’s imperfect, so programmers conclude that programs will fix humans. In a way, it’s a reassertion of importance. More often, humans fix humans. To adapt David Weinberger, the answer to user-generated data is MORE user-generated data.
****Probably there’s got to be some system to expire unused clusters.
*****UPDATE: After turning the feature loose I watched what new tagmashes would be created. One was children, cooking. Should I call the police?
Labels: new feature, tagging, tagmash