Archive for the ‘Projects’ Category

Macfarlane: Empirical Study of the Needs of Self-Represented Litigants in Canada

May 8, 2013

Professor Dr. Julie Macfarlane of the University of Windsor has published The National Self-Represented Litigants Project: Identifying and Meeting the Needs of Self-Represented Litigants: Final Report (2013).

The report states the findings of an empirical study of the needs of pro se litigants in courts in Alberta, British Columbia, and Ontario.

Findings are based on one-on-one or focus-group interviews with “259 self-represented litigants” (SRLs) and 107 legal service providers.

Although the sample is not a probability sample, “the characteristics of the SRL sample are broadly representative of the general Canadian population.”

The principal findings regarding information are as follows (I’ve added bulleted lists for ease of reading):

Regarding court forms:

The most common complaints include:

  • difficulty knowing which form(s) to use;
  • apparently inconsistent information from court staff/judges;
  • difficulty with the language used on forms; and
  • the consequences of mistakes including adjournments and more wasted time and stress.

Regarding online legal resources:

[SRLs] identified the following weaknesses:

  • an emphasis on substantive legal information and an absence of information on practical tasks like:
    • filing or serving,
    • advice on negotiation or a strategy for talking to the other side,
    • presentation techniques, or [...]
    • legal procedure;
  • [online legal resources] often directed them to other sites (sometimes with broken links) with inconsistent information; and
  • multiplicity of sites with no means of differentiating which is the most “legitimate”.

Cynthia Eagan [a member of the research team] found many of the same problems when she audited a selection of on-line Court Guides [... as well as problems concerning:]

  • the reading levels of some of this material (as high as 13.5), and
  • the heavy use of jargon and unexplained legal terms.

Regarding legal information for SRLs:

  • SRL’s in the study frequently described themselves as seeking “guidance” rather than “direction”.
  • The most common source of legal information for SRL’s are court staff [...]
  • [SRLs] complained about the restrictions on the time and scope of information that these staff can offer, because of:
    • the limitation on their providing “legal advice”[...] or [...]
    • the sheer volume of people they are dealing with.
  • The distinction between legal information/legal advice which lies at the heart of the job descriptions of staff working on the court counters and in information services is consistently complained about by both SRL’s and staff, as at best unclear and at worst practically unworkable [...]

Regarding access to legal services:

[...] many SRL’s sought some type of “unbundled” legal services from legal counsel; for example:

  • assistance with document review,
  • writing a letter, or
  • appearing in court [...]

For the recommendations and additional information, please see the complete report and the project’s Website.

Funding for the project was provided by the Law Foundation of Ontario, the Alberta Law Foundation, and the Law Foundation of British Columbia/Legal Services Society of British Columbia.

Please see the comments to this post for events and other information related to the report.

Good Law Initiative Launch Event, 16 April 2013: Tweets and Resources

April 16, 2013

This post links to tweets and selected resources from the 16 April 2013 launch event for the Good Law Initiative, a project of the UK Office of the Parliamentary Counsel.

The main page for the initiative appears to be called Good law – Detailed guidance – GOV.UK.

Click here for video of the event.

The Office’s announcement of the Good Law initiative is called Join the good law conversation.

Twitter tweets from the launch event are now archived in .csv format.

The Twitter hashtag for the event, and for other Good Law activities, is #goodlaw

On 16 April 2013 the Office published a new report entitled When laws become too complex: Review by Office of the Parliamentary Counsel into the causes of complex legislation, which is also called the OPC Good Law Report or the Good Law Report.

For more information about the Good Law Initiative, please see Good law – Detailed guidance, or Good Law Initiative: UK Government Effort to Make Legislation More Effective and Accessible.

HT @johnlsheridan

Good Law Initiative: UK Government Effort to Make Legislation More Effective and Accessible

April 3, 2013

The UK Office of the Parliamentary Counsel is launching “the ‘Good Law’ initiative, with the aim of improving the user’s experience of legislation,” at an event to be held 16 April 2013, at the Institute for Government, London, England.

The Twitter hashtag for the initiative is #goodlaw

Here are excerpts of the announcement:

Legislation is difficult. The volume of statute law and regulations, together with their piecemeal structure, level of detail, and frequent amendments, mean that citizens find law complex, hard to understand, and difficult to comply with. That can generate barriers to economic activity, as well as burdens for individuals, businesses, and communities. It obstructs good government, and it undermines the rule of law.

Efforts have been made to address aspects of the problem. Parliamentary Counsel has adopted a simple, plain English style. The National Archives have improved access to up-to-date legislation through legislation.gov.uk. The Law Commission has a programme of special Bills for law reform, consolidation and repeals. But the problem remains.

At this event, the Office of the Parliamentary Counsel launches the ‘good law’ initiative with the aim of improving the user’s experience of legislation. Join us to discuss what ‘good law’ means in practice. What do users expect from legislation? How can we make it more accessible? When is complexity in legislation desirable? And when is unavoidable?

I believe that at the launch event, John Sheridan of The National Archives will give a presentation about the role of legislation.gov.uk in the Good Law initiative.

For more information about the launch event or to register for the event, please see the event announcement.

Click here for more information about the principles underlying the Good Law project.

HT @johnlsheridan

Hagan: Open Law Lab

March 16, 2013

Dr. Margaret Hagan of Stanford Law School has launched Open Law Lab, “an initiative to design law – to make it more accessible, more usable, and more engaging.”

Dr. Hagan says that the Lab currently is a nonprofit collaborative project among law students.

The Lab’s work currently addresses:

For more information, please see the Open Law Lab Website.

HT @margarethagan here and here

Legal Document Cloud

March 15, 2013

There has been some discussion recently of a legal document cloud: a version, specifically for legal texts, of DocumentCloud, the online document repository for journalists that uses OpenCalais to perform semantic analysis and annotation of documents.

[Here is a recent example of the use of DocumentCloud to annotate a legal text, in this instance the U.S. federal district court decision, in the National Security Letters case.]

As he was leaving the Open Data Day DC 2013 hackathon, Alan deLevie tweeted about a legal document cloud.

In a Twitter discussion of this topic at the end of Open Data Day DC 2013, Jonathan Stray said that Docracy is a legal document cloud service, with version control. [Docracy has just opened a beta version of a new technology called The Document Genome, that performs legal document comparison, summarization, and versioning, for a number of applications including compliance.]

Stray also suggested using the Associated Press’s Overview platform to do classification (tagging) of legal document collections.

Then, on March 5, 2013, Alan deLevie posted a readme for a proposed legal document cloud, on GitHub. Here are excerpts of the readme:

What?

I’m trying to build a set of standardized tools for one basic task: Looping through lots of law-related text, processing it, and saving the results. [...]

Why?

Under the hood, you’ll get parallelism and remote code execution from IronWorker. This has several advantages over running this code on your laptop:

Performance. Splitting up the work into chunks is an obvious win.

Reliability. In the middle of a large processing job, and the power goes out and your laptop battery is about to die? No worries. Your job continues to run, with results stored safely.

Curation. The legal informatics/open government/open data communities are coalescing in a great way. Many standalone scripts are emerging for specific text processing tasks. I’d like this repo to be a central place where anyone can quickly make use of these great tools. Batteries included will lower barriers to entry.

Standardization. The legal informatics community could gain by adopting a standard project structure.

Verification. This builds off of point 4. Need to show how you arrived at a certain set of findings? This could be done in maybe ~20 lines of code.

I envision something as simple as installing a Ruby gem, adding some API keys, mixing and matching text processors to suit your needs, then running your corpus through in a simple loop. [...]

A related resource: in October 2012 Elmer Masters of CALI described his proposal for a new cloud-based repository of court decisions, called CourtCloud.

If you know of other information regarding a legal document cloud, please share it in the comments to this post.

[NOTE: Edited on 18 March 2013 to clarify that the idea of a legal document cloud was not discussed aloud at Open Data Day DC 2013 but was instead mentioned on Twitter by Alan deLevie as he was leaving Open Data Day DC 2013. HT @adelevie here and here.]

Lee: The inside story of Aaron Swartz’s campaign to liberate court filings

February 10, 2013

Timothy B. Lee has posted The inside story of Aaron Swartz’s campaign to liberate court filings, at Ars Technica.

The article describes Lee’s recent interview with Stephen Schultze about his and Swartz’s efforts to make U.S. federal court documents public.

Here is an excerpt:

A key figure in Swartz’s PACER effort was Steve Schultze, now a researcher at Princeton’s Center for Information Technology Policy. Schultze recruited Swartz to the PACER fight and wrote the Perl script Swartz modified and then used to scrape the site.

Until recently, Schultze has been quiet about his role in Swartz’s PACER scraping caper. But Swartz’s death inspired Schultze to speak out. In a recent phone interview, Schultze described how Swartz downloaded gigabytes of PACER data and how that data has been put to use throughout the last four years. Schultze told us he hopes the outrage over Swartz’s death will provide momentum for legislation to finish the job Swartz and Schultze started almost five years ago: tearing down PACER’s paywall. [...]

Click here for information about Schultze’s new Open PACER project.

For more details, please see the complete article.

HT @advocatesstudio

Aaron Swartz Memorial Grants to further development of RECAP open law repository

February 6, 2013

On 3 February 2013 an additional $10,000 for the Aaron Swartz Memorial Grants — which fund the development of the RECAP project aimed at increasing public access to U.S. federal judicial informationwere announced by Stephen Schultze of Princeton’s Center for Information Technology Policy.

Here is an excerpt from the announcement:

The generous folks over at Google’s Open Source Programs team have pledged to support two more RECAP-related project awards — at $5,000 each. These are open to anyone who wishes to submit a proposal for a significant improvement to the RECAP system. We will work with the proposers to scope the project and define what qualifies for the award.

There are several potential ideas. For instance, someone might propose add support to RECAP for displaying the user’s current balance and prompting the user to liberate up to their free quarterly $15 allocation as the end of the quarter approaches (inspired by Operation Asymptote). Someone might propose to improve the archive.recapthelaw.org interface, and to improve detection and removal of private information. Someone might propose some other idea that we haven’t thought of. You may wish to watch the discussion of a few of these initial ideas from our developer kickoff session.

Email info@recapthelaw.org if you are interested. Thanks again to the Think Computer Foundation and Google.

These grants are in addition to the original $5,000 in grants sponsored by Think Computer Foundation and the Center for Information Technology Policy at Princeton University, where RECAP was developed.

Click here for Stephen Schultze’s VoxPopuLII post explaining RECAP.

HT @harlanyu and @sjschultze

Glassmeyer: Free Law Users Group

February 5, 2013

Sarah Glassmeyer, JD, MLS, of CALI has launched Free Law Users Group, on the pbworks platform.

Here is the description:

This group is for sharing news and developments in the Free Law world. Primarily it will serve as a conduit for connecting librarians to the law tech and developer communities, in the hope that librarians will be able to increase involvement and share their skills and knowledge. It is also hoped that individuals in the Free Law, Open Law and Open Gov developer worlds will join in and see that librarians aren’t so scary and can be a valuable resource in their projects.

This website is a wiki. Please feel free to add anything of relevance. It will really only succeed if the community takes charge of it. This also means it is a constant work in progress so check back often!

HT @sglassmeyer

On a related note:

Tim Stanley of Justia has started a new Free Law discussion group on Google+.

Three Efforts to Crowdsource Amendments to the Computer Fraud and Abuse Act, in Honor of Aaron Swartz: Lofgren-Wyden, EFF, and ForktheLaw

February 3, 2013

At least three separate efforts to crowdsource amendments to the U.S. federal Computer Fraud and Abuse Act (CFAA) appear to have recently been launched:

[UPDATE: Daniel Schuman kindly just told me of a fourth effort: Professor Orin Kerr has been crowdsourcing revisions to the statute at Volokh Conspiracy. In addition, Meredith L. Patterson just told me that Fork the Law is run by a group, of which she and Nadim Kobeissi are members; the Fork the Law personnel are listed here.]

At least the first three of these efforts are being undertaken expressly in honor of Aaron Swartz, who, before his death, was prosecuted for alleged violations of the CFAA, among other statutes.

What’s notable to me about these efforts is their variety:

  • variety of leaders (official legislators, public interest lawyers, a programmer, a law professor)
  • variety of ideological perspectives (from moderate Democratic to libertarian)
  • variety of intended audiences (including a broad general Internet audience, civil libertarians, programmers, the legal community)
  • variety of platforms (a general social news site, a collaborative legal blog, the Website of a public interest law firm, a purpose-built site)
  • and a variety of tools with which public attitudes and comments are posted, aggregated, processed, and then re-published for further public input.

The potential value of distributed and parallel crowdsourced drafting efforts is also apparent. Holding these different drafting efforts, targeted at different audiences with different types of knowledge and experience, in public on the open Web allows each of these drafting communities to learn from the others and adjust its draft accordingly, while maintaining its distinctive perspective. In particular, each drafting community can benefit from both legal and policy expertise expressed in other communities. So certain of the potential information advantages of working on the open Web — notably increased quantity, quality, and diversity of input — seem very likely to be realized through these CFAA crowdsourcing efforts.

HT Alex Howard, Eric Mill, and Stephen Schultze


Follow

Get every new post delivered to your Inbox.

Join 97 other followers

%d bloggers like this: