Category: Legal Research
With WestlawNext (WLN) finally going live for law school faculty, librarians and staff yesterday afternoon, many law school librarians are finally getting permanent access to the much-hyped interface. This comes only a couple of weeks after Julie Jones's fascinating panel at the AALL Annual Meeting, "The Economics of Interface: Vendors Respond." Following presentation's by Thomson Reuters' Mike Dahn, LexisNexis' Molly Miller and Fastcase's Ed Walters, Larry Abraham of Fordham Law stepped up to the audience microphone and told the vendor representatives that their interfaces discourage users from using secondary sources, instead emphasizing primary law materials. Following Laurence's comments, a few other audience members (myself included) complained to the panel about how vendors treat secondary sources both within their systems and in training provided to subscribers.
With that fresh in mind, I wanted to hit on some specific problems I've encountered while searching secondary sources in WLN. My concerns aren't new. I mentioned them in my initial review of the product back in January. Specifically, when searching state-specific secondary sources, the results are often cluttered with irrelevant materials at the top of the results list. Here's part of what I had to say back in January:
The search algorithms for secondary sources are also problematic. When I select California as my jurisdiction, if there are California-specific resources available on my topic, those need to show up first in my results. Period. When I ran a search for the term "rape," the first 12 results were from "National" sources such as Am.Jur. Trials, Am.Jur. Proof of Facts, and several law reviews. More alarming, none of these were general overviews of rape law, but instead provided information on specific aspects of rape law in various jurisdictions. I discussed this problem with Mike Dahn, vice president of new product development at Thomson Reuters Legal. He assured me that this was not by design and that they were working to make sure jurisdiction-specific resources for a user's selected jurisdiction float to the top of search results, but as of now this isn't working correctly.
The problem I described then still occurs. Here's what the top search results for the Secondary Sources facet look like when I select California as my jurisdiction and search for the word "rape":

The first result from a secondary source covering California law doesn't appear until the 11th result. This means a researcher, despite having already selected a jurisdiction, has to wade through numerous off-topic, out-of-jurisdiction articles to find the ones that are on point for the search.
There is, however, a way around this problem. Having already narrowed the search results to the "Secondary Sources" facet, the left sidebar now displays additional filters. Find the one labeled "Jurisdiction" and select "California":

With this one tweak, the results reflect more of what a researcher expects to see when performing a jurisdiction-specific search:

The jurisdiction sub-facet illustrates part of the problem with the original set of results. Despite a researcher having selected California as the jurisdiction before running the search, WestlawNext still includes "National" sources in the results. In a state with fewer high-quality secondary sources than California — say Nevada — including these national sources is probably a necessary evil (though one would hope these national search results would be more on point). Just realize that if you want only state-specific resources you'll need to do that extra step of filtering.
Oddly, even if you narrow your search target to only "California Secondary Sources" by browsing the WLN sources before running your search, WLN still considers those national sources to be "California Secondary Sources," so you'll again need to apply a post-search jurisdiction filter to get true state-specific results.
But the problem with secondary sources in WLN doesn't go away by selecting a sub-facet. This refers back to another problem I discussed in January:
In these results, very little specific information about each source displays. Most of the time what a researcher sees is the title of the specific section, the title of the source, and a couple of text snippets in which the search terms are highlighted. Little to no information about where within that source the section appears shows in these results. For example, when a section of "Witkin and Epstein's California Criminal Law" title simply "Generally" appears, that's the extent of the citation information displayed. The precise article within "Witkin & Epstein" in which this section appears is nowhere to be found, so researchers won't know until viewing the document itself whether it's from an article about sex crimes, robbery or murder. The threaded information available in search results for statutory sections (Title, Chapter, Subpart, etc.) needs to be included in secondary sources as well, or else the results are confusing at best and unusable at worst.
Take another look at that last screenshot showing results from California-only secondary sources. This uses WLN's default "More Detail" display type. In these results, the first result looks to be the most relevant. After all, it is titled "Rape" in big bold print. The second and third results also look to be on point, but the information provided is rather cryptic about what specific crime they refer to. If the source in question isn't part of your subscription plan, the only way to find out if they're relevant is to click on each and incur an out-of-plan charge. Not exactly the best way to go about cost-effective research. Worse still, that first result — the one titled "Rape" — that looks so relevant? It turns out this is a section from an article about First Degree Murder that only discusses rape insofar as it pertains to the commission of a homicide. The second result ("Nature of Crime") is the only one in the top three actually from Witkin & Epstein's article about the crime of rape. The third document in the results ("In General") is, like the first, about homicide.
There is a more detailed view available than this one, but it doesn't solve the problem. To change the display type, go to the display options at the top of the search results (the icon showing one to three horizontal lines) and select "Most Detail":

Even with the most detail display available for search results, however, the full threaded information isn't included and it's still impossible to tell whether each result concerns the specific crime of rape without retrieving the document itself:

This isn't a problem so long as the source is part of your subscription plan and you can pull up as many documents as you want. But if "Witkin & Epstein's California Criminal Law" isn't in your plan, you might be faced with quite the dilemma when deciding how important it is to find the right document. Or perhaps you'll skip secondary sources altogether, jumping instead into the primary law results directly.
Truth be told, the more specific your search terms ("unlawful sexual intercourse with a minor" vs. "rape"), the stronger likelihood of having relevant search results float to the top. This is true of any search engine, and I'm not suggesting the search algorithm is the problem. It's the display. Given that general searches like "rape" are common in legal research, particularly when searching secondary sources, the lack of useful identifying information about a document is a problem that needs to be addressed by Thomson Reuters Legal.
I don't want this post to be interpreted as a negative review of WLN. Most of my review in January was positive and I stand by that overall opinion. WestlawNext is a vast improvement across the board over Classic Westlaw, and I don't share the opinion of many that it "dumbs down" legal research. To the contrary, I've found that it adds considerable power to most of the research I've done using the new system. Figuring out what database I need to search in Classic Westlaw doesn't mean I understand the sources of law any better. It just means I know what database I need to search in Westlaw.
But as superior as it is to its predecessor, it still has legitimate problems. The issues associated with secondary sources in WLN need to be highlighted. Even if Thomson Reuters opts to not fix these problems, we as researchers need to be aware of them. And as instructors — both in the classroom and at the reference desk — we need to be prepared to educate others about them, too.
In 2009, Wolters Kluwer (WK) launched a web-based legal research system called IntelliConnect. The site incorporated a wide array of WK's print content from publishing brands such as CCH and Aspen. Within the law librarian community, the product launch generated a lot of negative opinions. Seeking to rehabilitate the product's image, WK invited several law librarian bloggers to the company's offices in New York a few weeks ago for a day of presentations and meetings. Full FTC disclosure: I accepted the invitation, with WK footing the bill for my flights, hotel room and a festive Cinco de Mayo lunch, as well as providing a per diem to cover other meals and transportation.
My exposure to IntelliConnect since its launch has been intermittent. This parallels my experience with the company's print products. Services like CCH's reporters are primarily practice materials, and as an academic librarian who does very little research in the tax and business arenas that WK specializes in, use of these materials is hardly a daily event. Nor weekly.
It's for that reason that I think my reaction to IntelliConnect upon launch was more positive than a lot of my colleagues. WK had placed its materials online prior to IntelliConnect in a manner that essentially matched its print products, thus you needed to know what content each title contained in order to use the materials. Much like the classic Westlaw and Lexis, you needed to know where something relevant would be found before looking for it. IntelliConnect, however, incorporated federated searching with faceted results, allowing users who didn't know with any specificity where the useful content for a query was to search the entire system at once and find matching content regardless of its location or print title.
While I found this to be a vast improvement over the old system, the federated search model, and its accompanying move away from print organization, upset a lot of longtime users. And therein lies the seemingly unsolvable problem for Wolters Kluwer: How do you make all types of users happy?
Power users of IntelliConnect's CCH/Aspen/etc content know what's there, where it is, and expect the ability to go straight to it with as few clicks as possible. New and less frequent users than that group, however, might prefer a system they can log into and navigate with ease, guiding them to the material they're looking for even when they don't know where it is.
The initial launch played more to the needs of the latter group, with content organized by type (case, explanation, etc.), rather than practice area. This provided a major source of complaints from power users who wanted materials organized by publication title. Since the launch, WK responded to these complaints by reorganizing its content by practice area, a change that should make a big difference in usability to those users. Of course, for the non-power users this means the "CCH for Dummies" interface is gone. Personally, I wish the company could find a way to integrate both organizational models without one getting in the way of the other. I'm not sure how this could best be accomplished, and without a concrete suggestion to offer, I have to agree with WK that pleasing the existing user base has to be a higher priority for the company right now.
WK added a number of other features since the launch, including navigational enhancements like "next document"/"previous document" buttons, book browsing and full document path information for every piece of content in the system. All of these features are being added in response to user suggestions and complaints, while indicative of real problems in the initial product launch, demonstrates that WK is unusually responsive for a high end legal information vendor.
Beyond what's already been added, the company has several enhancements slated for release this year. In July the front page of IntelliConnect, currently a mostly blank screen void of useful content other than a search box will be replaced with a number of links to the user's "favorite" materials and a number of support documents that are currently buried within the system. More importantly, the system's "browse tree" will be visible on the front page, allowing users to immediately browse the system's contents without having to click the small "Browse" command first.
Also on the way is a "Titles A-Z" list that provides users an easy way to view and find every title included in the current subscription. Coupled with a "Title Finder" search box, this will finally allow a user to know what they've subscribed to without needing to navigate a confusing backend interface.
From a content perspective, IntelliConnect is a valuable practitioner resource, providing searchable electronic access to CCH's goldmine of looseleaf publications, as well as a number of Aspen publications. Despite the confusing branding on IntelliConnect's homepage (the URL says "CCH," the browser title bar says "IntelliConnect," and the page banner says "Wolters Kluwer), the company says IntelliConnect is intended to be the online presence for all of WK's legal information content, including (eventually) LoisLaw, the primary law database recently purchased by the company.
With all of these positives to recommend IntelliConnect, there is one aspect of the system that gives me pause: user interface. The layout of the system is something akin to a 1990's CD-ROM product running Folio Views. IntelliConnect's browse tree is constructed with threaded menus in which a user has to click on a small plus sign to expand the next level of the menu. The more levels down a user drills, the farther to the right the links are indented. And because this navigation pane is constructed with HTML panels, that means the titles become hidden behind the main content pane, requiring users to either scroll with a horizontal scroll bar or grab the panel's border and change the width of the nav pane. Is this functional? Yes. But it's not optimal nor is it in line with current web design norms.
The use of frames raises a larger issue than just the ease of navigation, which is overall browser functionality. One of the reason HTML frames fell out of favor in the last decade is that they render the URL visible in the browser's address bar unusable. That URL reflects the address of the page containing the frames, not the addresses of the frames currently loaded within that page. As a result, a user cannot copy and paste the visible URL into an email or another browser window or post a link to it on an intranet page so other users can access the precise material being viewed at any given time. Instead, if I email a colleague a link to the case I'm reading, when he or she tries to open it, it will load the IntelliConnect home page. In most situations, IntelliConnect's built-in email mechanism provides a workaround, but the functionality remains inconsistent that provided by most internet sites. The one place where there is no workaround is the browser's refresh button. If, as sometimes happens in IntelliConnect, a page doesn't load properly or freezes, users expect the refresh button to reload that page. Because frames are used, however, clicking the refresh button reloads the IntelliConnect home page, taking the user back to the beginning of the research trail. Frames can also break the browser's "Back" button (a common glitch in classic Westlaw), though this is less of a problem now than it used to be.
Another problematic issue with the interface is that it isn't compatible with all browsers. In fact, if a user loads IntelliConnect in anything other than Internet Explorer, a warning appears informing the user that he should use IE. While the system seems to work okay in Firefox despite the warning, it is effectively broken in both Safari and Chrome, with important buttons rendered unclickable or even invisible in those browsers. While many legal information providers rely on the accepted wisdom that all law firms are Windows shops that force employees to use only Internet Explorer, this ignores the realities of attorneys who prefer a different operating system or browser and ignore firm IT mandates when possible. And given what I see in the law school environment, where about 50% of students are now Mac users, as the current generation of students and young lawyers gain seniority in firms, the Windows-only mandates will evaporate. When questioned on the issue of browser compatibility, the folks at WK assured us they are aware of the problem and want IntelliConnect to be cross-browser compatible, no details as to what they're doing to fix the problem were offered nor a target date for when a fix would be in place.
Apart from technical concerns, the UI simply isn't consistent with design norms currently used across the web. This is a vague complaint to elaborate on, so I'll use an example within WK itself: AspenLaw.com. The colors, fonts, nav structure and browsing experience on this site are consistent with both contemporary concepts of what's "pretty" and what internet users have been conditioned to expect from popular sites like Facebook, Google or CNN. Upon selecting a publication series from the Student Central menu, the product listings are displayed in a two column layout, with facet navigation on the left and results on the right. Neither of these columns are frames. Each of the search facets list a few of the most popular categories by default, which tells the user what the facet title actually means, with a link to expand the list further if necessary. Selecting a specific item from the results loads that document in its own page with a permanent URL. To get back to the search results, a user need only click the browser's back button. No special training is required to navigate the site because it operates exactly the way most of popular sites do. AspenLaw.com illustrates that WK has excellent web designers (a distinct role that is separate from the web developers who actually build sites) at its disposal to design user interfaces for its products. I hope at some point the company asks them to tackle the IntelliConnect UI.
These UI complaints do nothing to detract from the high quality of IntelliConnect's content or the ways in which it organizes the content in response to user needs and suggestions. But with an updated look and feel that incorporates the ways users already navigate the web, the rich WK content provided in IntelliConnect could become not just functional but intuitive.
Last July, while traveling home from the AALL Annual Meeting, I had a layover in St. Louis. During this travel break I checked Twitter from my phone to see if anything conference-related had happened while I was in the air. Well, the best I could find was a vendor who had used a hashtag that some of my friends and I had used to identify our clique that week. In response, someone used the anonymous @aallsecrets account to criticize the vendor for co-opting "our" identifier, and I quickly fired off a couple tweets of my own belittling the vendor, even calling him a not-so-nice name. By then it was time to board my flight to Los Angeles, so I turned off my phone and forgot all about it.
While waiting for my luggage at LAX a few hours later, I checked Twitter again. My name-calling hadn't gone over so well. Someone called me out for rudeness from the @aallsecrets account, while the vendor in question explained that he used the hashtag as a way of inviting all of us to a party that evening, something I might have realized had I bothered to pay much attention to the content of his tweet. Nevertheless, I was angry at being called out. While crafting what I thought was a witty 140-character evisceration of anyone who disagreed with me, my phone battery died, leaving me unable to crush all opposition.
Before I could publish this brief manifesto, I discovered the airport police had towed my car from the long-term lot. By the time I made it home several hours later, my self-imagined feud with this vendor felt absurd, and I was ashamed of what I'd said. So when I did finally power up my laptop and return the internet, the first thing I did was email an apology to the vendor.
That episode of name-calling wasn't the first time I'd used the web to express self-righteous anger. By then it had become something of an art form for me. Any time I disagreed with someone, it was easier to tweet something inflammatory (and passive aggressive) than to communicate directly with the person I imagined I was feuding with. In the best of possible worlds, I'd raise an issue in the most condescending tone I could muster and start a revolution of re-tweets and replies that carried my message well beyond my own meager reach.
In the days following the namecalling incident, I decided I had some growing up to do and promised myself I'd stop making everything so personal in my communication with colleagues and vendors. Anger would not be my defining emotion and hyperbole would not be my preferred writing style.
My record since then has been spotty, but improved. I've only made a handful of passive aggressive tweets about AALL (one of my biggest targets in those heady pre-AALL 2009 days) in the months since, and I believe my blog writing since last summer has become more measured and logical than it was in the past.
But I'm troubled by the overall tone of our profession's communication of late. Now, flame wars are nothing new. The law-lib listserv has seen more than a few blow ups between librarians with differing opinions over the years, and Twitter might be unrecognizable without its piles of overreaction. (Just ask Scott Baio.) Nevertheless, I don't always understand the motivations of librarians who attack one another on a personal level and generalize vendors as evil empires with illegal intent. (Yes, any statement that a vendor is trying to bribe a state employee is an accusation of criminal behavior.)
The last week has seen some intense debate regarding vendor swag and librarian ethics. One need look no farther than the comments to any of Sarah Glassmeyer's posts on the subject (here, here, here and here) to see that there is a wide array of opinions on the matter and that we have no hesitation in challenging the moral integrity of one another in the process. Those that disagree with us are labeled "biased" and "trolls" rather than just a person with a different opinion. Exaggerated conflagrations become the norm on Twitter, with educated and influential legal information professionals questioning the character of our entire profession while providing no concrete evidence of our moral decay. And when an alleged employee of Thomson Reuters Legal (TRL), the grand villain in the eyes of so many librarians, posts a comment defending the company's marketing strategy without identifying herself as a TRL employee, there is an automatic assumption of so-called "sock-puppetry," with no consideration that the alleged employee might like her place of work and decide on her own to defend it. Instead, we feel compelled to unmask her treacherous ways in the most humiliating manner possible with no concern that we might put her job in jeopardy. (Never mind that IP addresses can be spoofed.)
There is, of course, the possibility that the commenter was a sock-puppet, and that's a troubling possibility that deserves investigation. As do many of the ethical questions raised in the last week.
But within the social media wing of our profession, vendor hatred has become a badge of honor. On the announcement of new products, sight unseen, we state publicly our suspicions that vendors designed such products to increase profits at the expense of effective research, never considering for a moment that maybe those two ends aren't always in conflict.
The inflammatory rhetoric lobbed at TRL, LexisNexis and others is sometimes well-grounded, but we've reached a tipping point where any opinion short of "West sucks!" is dismissed by many. We become outraged when a vendor attempts to bypass us in their marketing, as West did with a promotional email last year. Yet if vendors talked about librarians the way librarians talk about vendors, we would be up in arms.
I understand a great deal of the anger. I find myself regularly frustrated by the decisions made by many vendors, be they marketing, pricing or design decisions. But at the end of the day, we still have to work with these vendors. We have contracts to negotiate, products to vet and dollars to allocate. Sometimes the products are good, sometimes they aren't. (More accurately, sometimes parts of a single product are good while other parts of the very same product are bad.) Sometimes we are charged too much, sometimes we aren't. Sometimes we buy the product, sometimes we don't.
But we also have choices in how we respond to our anger, even the most justifiable anger. What law librarian interest is served in publicly shaming a vendor over a disagreement?
Society loves its villains. Tiger Woods can vouch for that. So can NBC. But what did Conan O'Brien accomplish by announcing via press release his rejection of NBC's time slot change other than winning public opinion? As much as I support Conan's decision to walk away from "The Tonight Show," I can't help but notice that even after the press release, he still lost his job and the jobs of his staffers and faced a contentious negotiation with the executives at NBC. Maybe if he had called Jeff Zucker and privately said, "No thanks, Jeff," instead of speaking to the "People of Earth" he might have obtained better severance packages for his staff, a larger payout for himself, a shorter non-compete period and the rights to some of his show's recurring characters. Perhaps not.
Intelligent people can disagree on just about anything, yet they can do so in a civilized manner. That's the kind of career I signed on for seven years ago when I decided to become a librarian. Since then I've been something less than perfect in that regard, but I'm trying. And when I arrive in Denver this July for the AALL Annual Meeting, one of the first things I'll do is buy a beer for the vendor I insulted last year.
| The Daily Show With Jon Stewart | Mon - Thurs 11p / 10c | |||
| The Blogs Must Be Crazy | ||||
|
||||
As I mentioned in my previous post, I traveled to Eagan, Minnesota (on Thomson Reuters' dime) earlier this week along with several other writers to get a sneak peek at Thomson Reuters' new legal research product, WestlawNext. I've already participated in a video roundtable discussion on the system, but I wanted to go into a little more detail in writing. Several others have provided comprehensive reviews of the product already, so I don't want to duplicate too much of their information. I do, however, want to look at things from the perspective of legal research instruction, since that's a big part of what I do in my job each fall, and because I've written in the past about Lexis and Westlaw's usability from that perspective over at VoxPopuLII.
The simplest assessment is this: Once law students gain access to WestlawNext (and "New Lexis," launching later this year), legal research instructors will have some 'splaining (or at least some adapting) to do.
Research instruction is marginalized and splintered at most law schools as it is. If law librarians -- the most qualified research instructors within any law school -- are part of a required 1L research curriculum, the length of that instruction is often brief. At Loyola Law School, for example, we have five weeks in the fall semester to cover the basics. At other schools, librarians might play no role. Instead, a legal writing program might rely on second-year students to teach the material. At the far end of the spectrum, some schools have no required research curriculum, offering only advanced research electives. Regardless of these requirements, electronic research instruction is often farmed out to vendor representatives, with Westlaw reps teaching Westlaw and Lexis reps teaching Lexis. The reliability of rep training varies, and a common complaint among librarians is that these reps emphasize full-text searching of primary law at the expense of secondary sources and other analytical materials. This leads to a somewhat disjointed program of instruction, even without the ground shifting beneath us.
When using the current versions of Westlaw and Lexis, a researcher needs to know exactly where relevant information is located before running a search. Therefore, when searching for primary law, she has to already know if she's looking for cases or statutes or regulations or some other type of document. In a familiar area of law, that's not a big hurdle, but when researching a new topic, the first task in research is often figuring out what type of law governs. Only then can the researcher move on to primary materials.
Using WestlawNext, however, a researcher no longer needs to select a source database before running a search. Instead, searches are most often limited only by jurisdiction, using a pop-up page overlay (NOT a pop-up browser window/tab) that allows precise selection of both state and federal jurisdictions. Then, upon running a search, the system provides results from all types of sources -- primary and secondary -- in that jurisdiction: cases, statutes, regulations, secondary sources, briefs, etc. The overview page shows just the first one or two results in each category, but the left sidebar of the page lists all the types of documents available with a count of the number of results in each of these facets. To see complete results for a particular type of resource, a researcher need only click the link for that category. When viewing these faceted results, more limiting options appear in the sidebar, such as jurisdiction, date, topic, and publication name depending on the type of materials being viewed.

Generally speaking, WestlawNext eliminates the need for researchers to know where to look for legal documents before running their searches. Don't know whether your clients' issue involves statutory or regulatory law? Just run the search and find out from the results.
To be fair, the current version of Westlaw already allows researchers to search multiple databases simultaneously, but the implementation is poor. Selecting the databases you want is a tedious process, the results display in one lump-sum list of results with no limiting facets, and basic functionality like tables of contents are nowhere to be found when viewing documents from your results. These problems are all dealbreakers, and they are corrected in WestlawNext.
While the relevant sources of law can be gleaned more easily from search results, it presents a challenge to legal research instructors. As legal professionals who have used the old systems (and print resources) for years, we already understand what the various sources of law are and how they work together. To even use Westlaw and Lexis, law students needed to learn this foundation. With WestlawNext (and most likely "New Lexis") providing Google-esque search with faceted results, students can and will run searches without an understanding of legal sources and yet not feel confused by the results. Well, not at first.
Given this likelihood, research instructors will have to provide a solid overview of the sources of law to their students. Hopefully, we already do this. But until now we could rely on Westlaw's database selection requirement to force students into learning at least a little bit about these sources before running a search that provided meaningful results. Not anymore. A student need not understand anything about sources in order to retrieve a wide swath of relevant material, and many will have the illusory feeling that the research process has been simplified enough to eliminate any need for foundational training. After all, if the fact pattern mentions "unlawful sexual intercourse" and "California" (yes, I used a Roman Polanski hypothetical in my class), a student can search those terms and retrieve a California case that seems to be on point and perhaps believe they've performed due diligence. Of course, the governing law might actually be statutory. Or there might be an split among appellate courts in California on the specific issue. Or a higher court may have decided an issue a little closer to the one in the fact pattern, making the case in hand irrelevant.
This isn't a criticism of WestlawNext. Assuming one understands sources of law, the search experience in WLN is more efficient and more likely to provide relevant materials in results. From a single search a researcher can pull in a wide array of materials and browse them easily using the provided facets. A lawyer unfamiliar with California real estate law need not know of the existence of "Miller & Starr California Real Estate" ahead of time in order to easily find that source's information in WestlawNext.
Foundational source issues are already covered in legal research instruction. The problem isn't that we don't teach them. The problem is that students might be less likely to listen once research begins to seem deceptively easy. This makes it all the more important for us to spend substantial time on instruction and assignments that cover the sources of law, independent of the specific research tools and mechanics. The good news is that if the WestlawNext interface is the future of legal research, we'll be able to spend less time in the classroom teaching Westlaw and Lexis navigation, providing extra time for foundational information.
Just because one can search an entire jurisdiction's worth of material doesn't mean that Thomson-Reuters Legal has eliminated the ability to browse and search more specific information. The currently buried Westlaw Directory once again moves front and center in WestlawNext (albeit in a redesigned form). Rather than running a search from the front page, a researcher can browse via simplified tabs on the front page (which thankfully contain no search boxes or checkboxes). From the "State Materials" tab, if a researcher selects California, a clean list of California materials displays, and the search box at the top of the page now limits itself to just a search of California materials. Clicking "All California Secondary Sources" displays a list of state-specific secondary sources and a search box that now searches only these resources. Selecting a specific source, say "California Jurisprudence," displays the table of contents for that source and allows searching of only that title.
It's been said elsewhere, but it bears repeating: Boolean search still functions. Given that many doubters have yet to acknowledge any of my colleagues' statements on this topic, let me repeat that: Boolean search still functions. There may still be some glitches here and there in that functionality, but Thomson-Reuters Legal has made it clear they intend for those operators to work as expected in WestlawNext.
WestlawNext is not without its problems, however, and the biggest concern I have is a big one for legal research instruction: secondary sources. No matter how many times instructors tell students to begin research with a secondary source, many students will still insist on running full-text searches of cases and statutory codes. (I was one of them.) Part of the blame lies at the feet of database reps who consistently overemphasize full-text searching of primary law in their training sessions, but anytime you ask students to find a case, the logical inclination is to, well, search cases.
I won't quibble with the order of the search facets in WestlawNext. Cases, statutes and other primary materials do belong at the top of the food chain because that's what lawyers and law students should be citing as precedent. The problem is how the results within the secondary sources facet display. In these results, very little specific information about each source displays. Most of the time what a researcher sees is the title of the specific section, the title of the source, and a couple of text snippets in which the search terms are highlighted. Little to no information about where within that source the section appears shows in these results. For example, when a section of Witkin and Epstein's California Criminal Law title simply "Generally" appears, that's the extent of the citation information displayed. The precise article within Witkin & Epstein in which this section appears is nowhere to be found, so researchers won't know until viewing the document itself whether it's from an article about sex crimes, robbery or murder. The threaded information available in search results for statutory sections (Title, Chapter, Subpart, etc.) needs to be included in secondary sources as well, or else the results are confusing at best and unusable at worst.
The search algorithms for secondary sources are also problematic. When I select California as my jurisdiction, if there are California-specific resources available on my topic, those need to show up first in my results. Period. When I ran a search for the term "rape," the first 12 results were from "National" sources such as Am.Jur. Trials, Am.Jur. Proof of Facts, and several law reviews. More alarming, none of these were general overviews of rape law, but instead provided information on specific aspects of rape law in various jurisdictions. I discussed this problem with Mike Dahn, vice president of new product development at Thomson Reuters Legal, he assured me that this was not by design and that they were working to make sure jurisdiction-specific resources for a user's selected jurisdiction float to the top of search results, but as of now this isn't working correctly.
Apart from these concerns, I'm still excited by the overall direction of WestlawNext. This really is a significant step forward in electronic research. I hesitate to call WestlawNext a "game-changer" because I think the game changed for all online search providers awhile back. Westlaw and Lexis are simply catching up, finally pushing legal search into the 21st century.
One final thing to note about the progress made here by Thomson Reuters (and presumably by LexisNexis later this year) is that it furthers the gap between the haves and have-nots in legal information. Once these new products are pushed out to law students, the more comfortable they become searching jurisdictions instead of sources, the harder it will be for them to use source-oriented tools (especially print materials). Again, this presents a challenge for those of us who teach legal research to make sure we provide them the foundation necessary to perform research on any platform.
I'm hardly the only person writing about WestlawNext this week. Here's a list of the reviews already in circulation:
Robert Ambrogi, A First Look at WestlawNext
David Bilinski, Dave’s Top 10 List about WestlawNext
Laura Bergus, WestlawNext: It’s About Time
Simon Chester, The Future of WestLaw – A First Glimpse
Jason Eiseman, 5 random thoughts about WestlawNext
Carolyn Elefant, My Trip Out [to] West: A Preview of WestlawNext
Greg Lambert, WestlawNext - A Study in Applying Knowledge Management & Crowdsourcing
Betsy McKenzie, Westlaw Next
Lisa Solomon, WestlawNext Preview: Product and Pricing
Jason Wilson, WestlawNext Review: Ending the tyranny of the keyword?
And of course, be sure to check out Jason Eiseman's video roundtable with Greg Lambert, Jason Wilson and me:
Video: discussion of WestlawNext
Last night while grading student assignments for my legal research classes, I encountered an anomaly in the text of California Jurisprudence 3d. I'd asked students to locate a secondary source discussing California's criminal charge of Unlawful Sexual Intercourse with a Minor. (Yes, I used the Roman Polanski case for my fact pattern.) For those who chose to use Cal. Jur., the experience differed depending on whether they used Lexis or Westlaw.
First, the section numbers don't match. In Westlaw, the general discussion of Unlawful Sexual Intercourse (which falls hierarchically at Criminal Law: Crimes Against the Person -> X. Unlawful Sexual Intercourse -> A. In General) begins at 18 Cal. Jur. 3d Criminal Law: Crimes Against the Person § 595. In Lexis, however, this same discussion begins at § 487 (found in the same hierarchical location). In the Westlaw version, there is a link to something called a "Correlation Table" which shows a column of section numbers aligned with another column of section numbers. Sure enough, in this table § 487 in the left column correlates with § 595 in the right column. Unfortunately, the table offers no explanation as to what this correlation is. I finally tracked down the explanation in the print edition of Cal. Jur., which reads as follows:
This table shows where the subject matter in the various sections of the former edition of California Jurisprudence 3d is set forth in this revised volume. This table enables the user to translate references found in the prior edition and other legal publications into references to this edition.
Thus, it appears Lexis's version of Cal. Jur. still uses the section numbers found in the former edition and have not been updated to reflect the numbering scheme in the revised volumes.
This is not, however, the only problem. The second problem with using Cal. Jur. in Lexis and Westlaw is that the text itself doesn't match. Take, for example, the first paragraph of § 595/487. In both Lexis and Westlaw, the first two sentences are identical:
The Penal Code defines unlawful sexual intercourse as an act of sexual intercourse accomplished with a person who is not the spouse of the perpetrator if the person is a minor. The provision further defines a "minor" as a person under the age of 18 years, and an "adult" as a person who is at least 18 years of age.
Both versions place footnote 1 after the second sentence. In Westlaw, the paragraph concludes with this sentence:
Unlawful sexual intercourse with a minor is a general intent offense.
Footnote 2, citing a 2009 California Court of Appeals case, appears here in Westlaw. Lexis, on the other hand, includes neither the sentence about general intent nor the footnote containing a citation to a 2009 case. Instead, Lexis continues the first paragraph with:
This offense was formerly incorporated in the section of the Penal Code defining rape, during which time it was often referred to by the courts as statutory rape.
In Westlaw, this sentence is in the second, not first, paragraph. The discrepancies continue from there, with sentences arranged in a different order depending on which system you consult. Further, Westlaw's version of the section has 13 footnotes, while Lexis's only has 10.
I'm not sure what the problem is at this point. Lexis includes a copyright notice at the top of its § 487 that reads "Copyright © 2009 West Group," and its Source Information page for Cal. Jur. states the following:
COVERAGE: Current
FREQUENCY: Annually
UPDATE-SCHEDULE: Within 1 day of publication
All of this suggests that the Lexis version should be up to date. Did the updates simply slip through the cracks and not make it into the system? Or did West fail to submit its updated text to Lexis? Or is it something else?
I sent an email to Lexis Librarian Relations earlier today explaining the problem, so hopefully there will some sort of explanation or resolution soon.
Who says grading can't be fun?
Being on the west coast, and a late riser to boot, I often wake to discover interesting debates about library issues well underway — or even winding down — among my law librarian colleagues on Twitter. Today's topic (initiated by @montserratlj) was a common source of discussion: collecting and maintaining print journals that are available electronically. This is a sticky issue for a number of reasons.
First, it's expensive to maintain journal titles in both print and electronic formats. As time passes, more students simply expect articles to be available online. This preference for electronic materials is often so strong that they give up a line of research when informed that it's only available in print. Conversely, many faculty still strongly prefer print materials, whether due to personal preference or because a title's electronic version sometimes doesn't include everything found in the print copy (e.g., photos, graphs, etc.). Making both groups happy means devoting institutional resources to redundant collections, which sacrifices a library's ability to collect a wider scope of materials — in any format.
Second, given that electronic access to law journals, even those edited by a law school's own students, is usually provided only by commercial vendors on a subscription basis, there is little guarantee of permanent electronic access to a title. With print, however, so long as the library takes care of its periodical collection, a title will be available in perpetuity, regardless of whether the publisher (or even the publishing law school) folds or the subscription is cancelled.
Library directors at 12 leading law schools raised these concerns when drafting the Durham Statement on Open Access to Legal Scholarship, "which calls for all law schools to stop publishing their journals in print format and to rely instead on electronic publication coupled with a commitment to keep the electronic versions available in stable, open, digital formats." As should probably be the case in such a call to action, the Durham Statement leaves open the question of what format is best suited for creating "stable" and "open" repositories, though given economic pressures and digital solutions that vary from school to school depending upon the preferences and expertise of an institution's IT staff, a lack of guidance on this issue could lead to delayed progress or incompatible systems.
In recent years, many law reviews have already begun posting PDFs of their articles online for free. This is hardly a universal movement, and such open availability can vary wildly even among publications produced at the same school. Access is often limited to browsing tables of contents, with no search functionality to be found. In most cases, these efforts are taken on by the journals themselves. While the initiative of such student staffers deserves our praise, there are certainly limits to what they can realistically accomplish. For example, given the transitory nature of law review staffs, there is little incentive to look beyond the digitization of the current volume, let alone establish a consistent system for subsequent years or plan a long term effort to digitize previous volumes. In addition, the easy solution is PDF-only, which is hardly a well-structured data format for any purpose other than sending a document to the nearest printer. Even when the time is taken to OCR these documents, or when the PDF itself is generated through a word processor (eliminating the need for OCR), one's ability to find anything is still nearly impossible without robust metadata. One needs to look no further than the latest Google Books kerfuffle to understand the importance of metadata for online research.
If metadata, structure, and permanence are vital to the success of the Durham Statement's desired action, librarians must do more than simply ask their institutions to create digital access systems for law reviews. What the Durham Statement asks schools to create are digital libraries. If librarians willingly cede the design, implementation and maintenance of these new libraries to IT staff and law students, it's a troubling statement about the future of our profession. Far too many commercial research vendors have bypassed librarian expertise in the creation of their online systems, and we end up with expensive databases that are difficult to use and fail to take into consideration how the content itself is utilized in research. By allowing this creative process to spread within our own walls, we are effectively putting our stamp of approval on it and relegating ourselves to increasing irrelevance in a digital world. In a world where "cutting out the middle man" is desireable enough to researchers that it becomes a marketing point, digital library design becomes a far more important aspect of our profession.
Many will be tempted to look to institutional repositories as the great hope for open electronic access to law reviews, but they're not. IRs serve a vital importance as preservers of a law school's scholarly and cultural output, and the IR efforts of institutions like Duke and Georgia should be models for every other law school in the country. IRs don't address reputational economies, nor should they. What defines an article's inclusion in an IR has nothing to do with who publishes it. It's about who wrote it. Thus, in an IR articles from Yale Law Journal should arguably have equal standing to working papers that never receive publication elsewhere.
However, in a world where electronic access to legal scholarship is limited to institutional repositories, where there is no measure for the prestige of an article, a tenure track faculty's worst nightmare is realized. A common criticism of electronic only publication is that it is inherently less prestigious than print. Non-tenured faculty are often advised to shun blogging for this very reason. But this argument only applies to electronic publications that lack a rigorous editorial process. If Harvard Law Review changes nothing other than its publication medium, keeping intact all its selection and editing processes, will the articles it publishes lose their prestige simply because they're electronic? That seems rather arbitrary.
(In a perfect world that makes me drool at the possibilities, each law review could simply be a UI layer that pulls its articles from the author's original institutional repository, but that's a tangent for another post. As is a discussion of why data standards are essential to both.)
When it comes to the Durham Statement, let's do more than sign it. Let's put our money where our mouths are. Assuming that permanent, open access to electronic law reviews is a desirable goal, librarians are the best professionals to make that happen.
Yesterday saw a lot of outrage from the law librarian community, thanks to a new (albeit short-lived) promotion from Thomson West that read in part:
Are you on a first name basis with the librarian? If so, chances are, you're spending too much time at the library.
(Click here to view the full ad)
Let me say up-front that I don't think this was a smart marketing strategy for West. Law librarians certainly play a role in throwing a sizeable chunk of change West's way, even if we aren't their biggest audience. Yet, while the ad isn't as disparaging on its face as some have complained (e.g., it doesn't really say anything negative about librarians), singling out a customer constituency in this way would be ill-advised for any company.
With that out of the way, let's look at this from a legal researcher's perspective. I tend to agree with the premise in West's ad that self-service research from one's own office is preferable to any situation that requires help from a librarian. Why do patrons talk to librarians? Because they can't find what they're looking for. As Terry Martin -- a law librarian -- said at a 1996 AALL "Town Meeting:"
Inevitably, there will be instances when people have got to ask a librarian for assistance. Now, I always think that this is a systems failure to some degree. We trained them improperly; we haven't designed a good catalog; and we haven't arranged materials well so that they can't help themselves.
Reprinted in Towards a Renaissance in Law Librarianship (Richard A. Danner, ed. 1997).
In a perfect (though certainly non-existent) world, if everyone involved in creating the system (law librarians, legal publishers, research database vendors) does his or her job right, a legal researcher would never need to ask a librarian for help.
That hardly means law librarians become irrelevant, but to remain a vital part of the system, we need to put as much effort in continuously re-designing and re-implementing that system as we do in helping lost researchers, because reducing those systems failures will save researchers time and frustration. Expressing outrage towards West for suggesting that self-service research is a good thing seems to indicate more concern on our part for the collective law librarian ego than for our patrons' needs.
You want to be angry at West for that ad? Be indignant at the suggestion that their online systems are comprehensive enough or designed intuitively enough to eliminate the need for librarian (or West's own customer support) assistance. Be outraged that they charge so much for their services that, no matter how well designed, our library budgets are the only thing that makes it possible for researchers to use them.
But never forget that if West, Lexis or some other legal database vendor ever fixed these problems, the need for our expertise, at least in its current form, would be reduced dramatically.
If West rethought its pricing structures and realized it could make a lot more money selling, to name one example, a Black's Law Dictionary iPhone app for $10 than it does for $50, a lot more patrons would buy their own research tools instead of relying on our deep pockets.
And if West put the energy and UI expertise responsible for its Black's Law Dictionary Digital software to work redesigning the Westlaw interface from the ground up (rather than simply dumping voluminous full text resources into its system with little regard for how they're used), there'd be a lot fewer questions at the reference desk about how to find something on Westlaw.
Are either of these things likely to happen anytime soon? History suggests they won't. But as I said yesterday on Twitter, I don't like relying on someone else's incompetence in order to stay relevant.
Truth is, West's questionable promotional piece advertised a world that, I believe, most researchers find appealing. Not because librarians are bad or unhelpful, but because research becomes far more efficient when someone finds what they're looking for without needing to ask for help at all. As Martin said, some system failure is inevitable. But that doesn't mean it can't be reduced. If an ad suggesting that such a reduction is positive scares librarians so much, my only question is, "Why?"
Working in an academic library, I routinely fill document requests for faculty. Sometimes a request is for a single article. Other times it's a list spanning several pages. The request list I'm working on now, for example, contains 25 articles. Fifteen years ago, this would've meant photocopying all 25 and hand delivering them to the faculty member. These days, with most articles available in PDF via electronic databases, the usual delivery method is email. With 25 articles to send, however, that can get tedious. Odds are good that my school's email system has a low enough file attachment size restriction that I'd have to split the documents into multiple emails. Even Gmail's higher size restrictions probably wouldn't suffice.
In recent months I've all but stopped sending email attachments to faculty. Instead I'm using a tool called Dropbox to store the documents. Then I just send an email containing each file's URL to the faculty member who requested the articles. When she clicks each link, she downloads the article directly from Dropbox.
So what is Dropbox? From Techcrunch:
The idea behind Dropbox... is that little to no effort should be put into keeping your desktop files synced with “the cloud”. So the three founders have built a... desktop client (available for both PCs and Macs) that acts like a regular folder on your machine. You can manage files within this folder just like elsewhere on your machine (add, edit, copy, and delete them) and changes will be automatically synced to Dropbox’s Amazon S3-backed storage, and very quickly at that.
So, in other words, when I save a file to the Dropbox folder on my office computer, it's automatically synced to the Dropbox folder on all my other computers, like my laptop or my home desktop. This isn't just a virtual folder, like with Apple's Mobile Me service. The file is actually transferred to my other computers, so I can access it even when I'm not online. That same file also becomes available on any other computer simply by logging into the Dropbox site with a web browser.
Each Dropbox account includes a "Public" folder, and that's where I place documents I need to deliver to faculty. Each file in this folder is assigned a unique public URL, and if I share the URL for a particular file with a faculty member, she can then download the file, even without her own Dropbox account.
Overcoming file attachment restrictions isn't the only benefit to this method of document delivery. In the past when I sent files by email, I still saved a copy to my computer for future reference (in case the faculty member accidentally deleted the email attachment and needed the article again). Since Dropbox's Public folder resides on my computer, I now simply use that folder as my faculty document archive and, thanks to auto-syncing, it's automatically available to me everywhere. Plus, anytime a faculty member needs to access an article again, she need only click on the link to it in the original email. Essentially, this folder becomes a shared folder of research between faculty and their librarian liaisons.
Dropbox offers a 2GB account free of charge, or you can upgrade to a 50GB account for $9.99/month or $99.99/year.




