Last week, I shared that Dan Katz and I had finally published a draft of our paper, Measuring the Complexity of the Law: The U.S. Code. We'd previewed this research on Computational Legal Studies years ago. Since then, we've received great feedback and a number of questions. The most common question, even among legal professionals,
Four years ago, Dan Katz and I began working on a project to measure the complexity of the law. Its genesis was, in every sense, an accident; in order to properly identify citations to the IRC in our VTR empirical review of U.S. Tax Court decisions, we had to deal with the informal, non-Blue
Live from ReInvent Law Silicon Valley, where I gave an Ignite-style talk drawing analogy to law's future from finance's past. Slides embedded below and video forthcoming:
After a nice twitter conversation this morning, I finally got the impetus to release the source for my Congressional Bill Statistics data. You can find the source at this Github repository. I haven't taken the time to review licensing yet, but I won't be asserting anything more than CC3 Attribution on my code.
Tonight, Eric and I will be presenting back-to-back talks at the AWS Michigan meetup (hosted by the Tech Brewery this time). Eric will be detailing a large Matlab HPC experiment we ran this summer to optimize parameters for a trading strategy; this one is a great AWS case study, as we crunch 10B inputs
Here's a wordcloud of the NFIB et al. v. Sebelius et al. opinion. Very interesting coalitions formation. Healthcare/ACA wordcloud If you're interested in the R and Java code for generating these wordclouds, please see my post on Arizona et al. v. United States from earlier in the week.
Here's one purely for fun - a wordcloud built from the Supreme Court's opinion on Arizona et al. v United States. Word clouds, though certainly not the most scientific of visualization techniques, are often engaging and "fun" ways to lead into discussion on NLP or topic modeling. Arizona et al. v United States wordcloud
You may have noticed that I keep talking about eDiscovery consulting and legal search in the cloud. I've covered searching the Supreme Court with new technologies in analytics and the cloud, making certain types of emails searchable on Amazon's cloud, and even eDiscovery and the cloud at a high level. While these posts are
In my last post on CloudSearch and eDiscovery, I described something like “Google” for eDiscovery emails. FedEx or DropBox your data to an eDiscovery service provider like myself, and rest assured that you’ll soon have a powerful, web-based user interface for searching and visualizing your digital discovery materials. As a technical follow-up to
In the last post on AWS CloudSearch, I provided a tutorial on the creation of a simple CloudSearch domain for Supreme Court decisions. This walkthrough described the steps of creating a domain, configuring access policies and indexing, populating the index, and using the search API. We were left with a functioning case search database.
