The LC's new search
Check the Library of Congress' new search, designated "beta."
It's got some great features:
*From the error results, I'm wondering if they're using Z39.50 to access their own catalog?
**Character-set sorting issues?
***LibraryThing would say "sort: title | author | date | scrumptuousness," making a message double as a UI element; the new search has no alternate sorting, however.
****Pardon the rant. This is a real bête noire of mine.
It's got some great features:
- "Federated" searching of different "buckets" of content, including the online catalog, prints and photographs, and the LC website.
- A refreshingly clean, simple and attractive interface that works just as you expect—it's Google-y!
- Rather than wait for everything to come back from the different systems, the search results Ajax in. It's slick, and a good way to avoid making the system hostage to whatever sub-service is sluggish that day.
- Eventually results dump you into the original systems. Obviously, they weren't trying to reengineer everything. Maybe, if the elegant new search becomes popular, it will prompt action to improve the online catalog itself.
- It presents only a few catalog results by default, and they aren't relevancy-ranked. (I don't think they've done anything to the search per se, but just "pulled it in" to the new UI.*) So, search for "cookery" (the LCSH term for "cooking") and you get four hits, all in what I take to be Burmese, apparently because of character-set sorting issues. Just image if Google returned results like that!
- "Word junk." You don't need to say "Note: These results are sorted in alphabetical order," you can just say "These results are sorted in alphabtical order," "Results in alphabetical order" or even "sorted alphabetically."*** A little message below a heading and above a piece of content is by definition a note! Do street signs say "Street sign: Main Street"? Ditto messages like "Select Sources to Search" over a list of sources above a search box. Say "Select Sources," "Search" or go cold-turkey. And, while we're on the topic, someone should cut the capital-letter budget. Capital letters have a grammatical role in sentences. Treating them as all-purpose markers of authority and importance misunderstands orthography as design. In design, "header-ness" is communicated by size, positioning and other visual factors. In any case, Studies, Have Shown that Reading Slows Down When Information is put in Unnecessary Capital Letters. So, how are you doing?****
- Brobdingnagian ULRs. 143 characters for an all-sources search on "cookery"? On the plus side, the URLs appear permanent, rather than the LC's usual "expiring" URLs.
*From the error results, I'm wondering if they're using Z39.50 to access their own catalog?
**Character-set sorting issues?
***LibraryThing would say "sort: title | author | date | scrumptuousness," making a message double as a UI element; the new search has no alternate sorting, however.
****Pardon the rant. This is a real bête noire of mine.
1 Comments:
Just image if Google returned results like that!
-"Just imagine"?
Speaking of Google, I'm surprised LOC haven't included a spellchecker, it certainly isn't hard to do...
*From the error results, I'm wondering if they're using Z39.50 to access their own catalog?
- Looks like it from the Javascript as well.
Maybe, if the elegant new search becomes popular, it will prompt action to improve the online catalog itself.
- We use the same Library system to manage our library and we are extremely limited with what can be done in the OPAC interface. LOC's options are either to write a Z39.50 inteface (which it looks like they have done), wait for the vendor to give them a better more customistable interface, or change library systems (which would be a mighty big job I imagine).
**Character-set sorting issues?
- I'd say so, once again probably related to the Z39.50 interface rather than "New Search" specifically
Post a Comment
<< Home