Where I’ve Been

Hi, How Are You?

It has been a while since I’ve had anything to say in public – the Lincoln quote about being thought a fool and all that – and I am not sure much has changed. I near the end of a third year as an academic law librarian, having learned much, having plenty more to learn. I teach, research, read, and maintain library tools and collections. I go to meetings. I walk around. In my free time, I work on coding skills and try to learn the ways of mindful self-support and self-compassion. I watch sports on television. I do the dishes. I sleep.

I Don’t Do Social Media

You won’t find me on the social media platforms any more. I miss the genuine connections I built with people and am grateful for the opportunities afforded by them, but the bad outweighed the good, and I tend not to be one for shades of gray, especially when it comes to behavior I feel is not allowing me live the richest life possible. There’s plenty that others have said on the topic that I won’t repeat, but in short, I have stopped twitting myself. Oh, and I do miss the constant affirmation and sense of belonging. That part is not so fun.

I (Try To) Make Computers Do Things

It’s no secret I’ve been learning to code with Python for the past two or three years or so, in fits and starts. The past several months have seen me rededicate myself, doing a version of what I must imagine Paul Ohm & Jonathan Frankle ask their students at Georgetown to do. I have done parts and wholes of several courses, but am focusing on strengthening my fundamentals. I’m learning more and more about working with files and directory structures across platforms, and about object orientation. I still like Zed, even if he is angry about strings, but Head First Python (2d) has helped me the most. I tried MIT’s 6.00.1x, but still cannot do math, which is sort of a problem!

I Support Open Web Technologies

I’m trying to add web skills to the mix, and have been working on [the resources available within Mozilla’s web docs platform] (https://developer.mozilla.org/en-US/docs/Learn). Essentially, this means HTML5, CSS3, and JavaScript, which is new for me. So many curly braces. And server-side scripting. In the midst of all this, I believe in supporting the open web, so while it ain’t perfect, I give some money to The Mozilla Foundation. I like OSS just fine, too, and run Ubuntu at home, though I prefer to send my cash to the Python Software Foundation and the Linux Foundation. And, of course, to developers who make useful tools – pay for what you believe in.

I want to learn more about how to collaborate on library-specific coding projects, too.

I Read, I Rest, I Drink Tea

Mostly mysteries, 19th century novels, and instruction manuals. Mostly on the couch. Mostly PG Tips.

Bye For Now

I’ll try to write more often. There’s plenty to share. Projects I’ve been working on, things I’ve been thinking about, etc., etc. Send me a message – I’m not too hard to find.

Crushed by bepress

At the outset, let me state explicitly that these are my opinions, insofar as one can develop opinions of one’s own. There are a lot of assumptions buried in what follows, many of which I am (painfully) aware of. Also, these are initial impressions, but I stand by them as what they are. [Some edits made for clarity.]

The Press

The Press

Elsevier acquired bepress, the company that offers the Digital Commons repository platform, which my institution purchased in 2015 shortly after I was hired, and to some degree at my urging. I am an academic law librarian at a large public institution. I have a little more than two years of experience in the field and in this job. Many academic law libraries have Digital Commons repositories.

At the time we signed on to Digital Commons, we had no mechanism for posting well-described full-text documents to the web. At first, we focused on uploading articles already published in student-run law reviews at our institution and then planned to move on to our faculty members’s scholarship (both published and drafts / working papers / pre-prints). Later, we would add unique collections of primary law documents. In the course of 18 months, I managed the repository and uploaded 6,000+ documents, which have been downloaded 160,000+ times.

Digital Commons offered a mechanism for uploading many documents at once and promised an easy-enough way of mediating document intake. The wider institution was working on a large project with a homegrown repository system that would meet the needs of all university faculty wanting to comply with the (voluntary) OA policy. Our library does not work much with the campus libraries — it is, like many law libraries, an independent entity on campus. Law libraries serve legal scholars, law students, and members of the public. Law publishing patterns, including those for scholarship, are considerably different than those in other areas of study or work, as are the needs of our discipline’s scholars.

I have about eight or ten different job duties, one of which is the maintenance of the repository. Overall, I’d say it makes up about 25% of my job, which also includes teaching advanced legal research, providing reference services to library patrons, working with the OPAC, etc., etc. I have some competence in computing — I know basic python scripting, which I have taught myself since starting this job. I know my way around the command line, too. I am a legal subject-matter specialist (and, not that it matters, a lawyer). And I am terrified.

First, it’s my responsibility to make sure as many people as possible have access to work produced by our faculty and student journals at the lowest cost possible. At the time I advocated we use bepress, I figured that the fee we pay for Digital Commons plus my part-time labor were acceptable trade-offs, in cost, for being able to make a lot of information free for the public to access. Maybe I was right, maybe I was wrong, but the fact is we got a lot of documents up quickly and people accessed them. Digital Commons was a fine solution — not perfect, but functional — but it was, and is, a for-profit publisher. With the Elsevier acquisition, I don’t know if it is as good a solution any more, for any number of reasons: increased cost, negative perception by the faculty, deprecation of the product….

But what are our options otherwise? I see two: (1) my law library joining in with the campus project, where, because of our difference as a law library, we will not likely get what we want (ease of use, control, etc.) and we will compete for attention with other, flashier scholarly areas or (2) joining some kind of pan-law-library consortial effort to build “our” own pre-print and repository management system. For the first, let me say that I admire the hard work and progress that has been made on campus — the university-wide repository is an amazing work of collaboration and engineering. For the second, let me say that I admire the consortial work that has been done preserve legal documents, share resources, and yes, the new partnership with OSI known as LawArXiv, which is still very much in early days.

The question I have is this: will it really be possible to muster the will, buy-in, and know-how to make either (or both) of these non-commercial options worthwhile for my library? I imagine that both will be costly in terms of money and time, and that neither will be as easy or as customizable to my needs as Digital Commons is. But neither will have the stink of Elsevier that is anathema to so much of the academic and legal academic community. I understand that my hard work — hours and hours of creating descriptions and uploading documents will be co-opted and sold back to me by some multinational corporation. That’s life; things are hard, the rich get richer, and we struggle to stay afloat. But I care about my patrons — the public — having access to information in a way that works for them, not for me or for my ideology.

So while the gotchas and the schadenfreude and the quick answers are fun, the truth is that we have a complex problem on our hands, and that there’s lots of work to be done to meet the public’s need not only for legal scholarship but also for other types of legal information. It’s not fun, it’s just hard.

File Naming Conventions for Court Documents


Summer is coming, and I’ve embarked on a research project concerning documents from the U.S. District Courts. As I was consolidating my work this morning, I grew frustrated with the naming conventions (or lack thereof) I’d been using while saving PDFs to drive. And since I have been rather, er, interested in filenames recently, it seemed as good a time as any to collect my thoughts. I will begin with the caveat that while I am a librarian and professor of legal research, and a successful applicant to the N.C. bar, I have never worked on a case as an attorney, so I am hoping to solicit some feedback in the comments below. I plan to keep this post updated with new information as it becomes available. So, let’s begin!

Federal Courts

U.S. District Courts & Bankruptcy Courts

An Example

The first federal district court document I found was a complaint from the Middle District of North Carolina, filed in 2016 and assigned the docket number 1:16-cv-00988. Here are two examples of how I would name this file:



Because the 94 federal district courts all use the same docket numbering pattern, it is essential to start the file name with an abbreviation for the court. I chose the abbreviation that the U.S. Courts uses for its websites — i.e., http://www.ncmd.uscourts.gov/ — which I like because it should always make it easy to sort by state alphabetically. Then, an underscore, followed by the docket number divided all by single dashes at the appropriate points. (Incidentally, this piece of the citation is considered “valid” by Bloomberg Law’s docket search feature, which is an added bonus.) Finally, the docket number, which should always be four characters, and prepended with as many leading zeros as is necessary to achieve this. If it’s important for you to be able to tell, at a glance, what the document is — i.e., an order, a memorandum in support of a motion, etc., etc., you should develop some kind of vocabulary for naming the document and add that after the docket number.

This naming scheme will allow you to easily parse your filenames and get them into a structured data format like a .csv file or Excel spreadsheet, if you’re going to be doing any analysis; greater structure will also help if you use a citation management system while writing. Of course, you can simply sort your directories by filename alphabetically and likely get a good picture of what you’ve got.

Creating Directories

For cases in the federal district courts, I’d also recommend creating directories for each case or matter that is being studied, but only if that case is particularly significant to your research or you have collected a lot of documents related to the case. I’d recommend using party names and eschewing the lowercase directory naming convention. For the document I’ve been using as an example, the directory would be Calloway-v-Moore and you would place documents from subsequent appeals or docketings, and presumably would also be useful if the case had been removed from state to federal court or if it had been transferred.

Bankruptcy Courts

My solution for documents from Article I U.S. Bankruptcy Courts follows the exact structure as above, using the url abbreviation from the federal court system website. A case from the United States Bankruptcy Court for the Eastern District of North Carolina would begin with NCEB. I will try to compile a simple chart of all the abbreviations used in federal court urls.

U.S. Court of Appeals

An Example

There are thirteen courts that make up the circuit courts of the U.S. Court of Appeals. Eleven are numbered geographic circuits, which leaves the DC Circuit and the Federal Circuit. I find it considerably easier to name files from these courts, however, there is a wrinkle concerning the case citation. Here are two examples of opinions I have collected:



The first component is rather self-explanatory — a two digit designation for the numerical circuit followed by CA. For the DC Circuit, I recommend DCCA and for the Federal Circuit, FCCA because, well, I am allowed to be arbitrary and there doesn’t seem to be a likelihood that either abbreviation will conflict with other abbreviations used in the legal field. Also, each is four characters — consistency! [Though Rachel Gurvich, a colleague and legal writing professor at UNC, pointed out that she uses CTAF, which is the four-character abbreviation used by Westlaw for Federal Circuit cases. Just pick one and stick with it!]

Next, we have a four-digit year notation for the date the opinion was filed. Following that is the case number or case citation, which will depend on what is available and perhaps on your own intellectual bent. Opinions from the U.S. Court of Appeals are published in West Publishing Federal Reporter, but, more recently, have been published directly by the court on its website or collocated and served from a site like govinfo.gov. If you have a document from the Federal Reporter (now in its third series, so F, F2d, and F3d will be appropriate abbreviations), I recommend following the Volume-Reporter-FirstPage model of citation. If you have any other federal appellate opinion, I recommend using the case number followed by an underscore and the case name format discussed above. Of course, appending the case name might be helpful in the case of an opinion in the Federal Reporter.

Again, the idea here is not to make your filename look like a Bluebook citation, it is to make it easier for you to draw meaningful information from the filename alone and to facilitate parsing of the data you’ve collected for any number of important purposes.

U.S. Supreme Court

Naming a case from the U.S. Supreme Court is rather straightforward — US followed by the four-digit year of decision, the case number, and some kind of descriptive phase about the case. These two names, representing recent cases in my collection, serve as examples: US_2014_13–354_Burwell-v-HobbyLobby.pdf and US_2016_15-108_PR-Sovereignty.pdf

State Courts

North Carolina

There is more on this to come in a subsequent post, but in the meantime, check out some data that was pretty easily parsed out from the information provided by the N.C. Administrative Office of the Courts concerning N.C. Court of Appeals opinions.

I will only discuss naming files from state appellate courts here, and will use North Carolina as an example. For state trial court documents, I’m afraid we will need another extremely long and boring blog post.

Intermediate Appellate Courts

Here is an example of a filename for a document from a state appellate court:


This case, from the North Carolina Court of Appeals, was interesting to me because it involved a quantum meruit claim for an attorney’s services. It’s the only 2017 case in my collection about an attorney fee dispute, and the party names weren’t significant to me, so I used a descriptive phrase. Pretty straightforward. If your state has multiple intermediate appellate courts, I recommend coming up with a two-character abbreviation. Please leave it in the comments below! For those of you regularly practicing in the nine states lacking intermediate appellate courts, I have just wasted a minute of your time.

Courts of Final Resort

I recommend using SC as the abbreviation for North Carolina’s Supreme Court, rendering a file name as such: NC_SC_1980_299-NC-360_Ragland-v-Moore.pdf

Here, we have an opinion from 1980 — but, because of the nature of the publication of state court opinions, we have a complication. Most states have both an official reporter for decisions and have decisions published in West’s National Reporter System. I suggest that, when possible, you use either the case number or the official reporter to use in your filename. The reason is that both citations are more rich in data at a glance than the regional reporter citation. There’s a lot to say about medium-neutral citation here, but my purpose isn’t to give a lesson in that whole mess, but rather to suggest an efficient and useful method of naming files so you can find them easily and analyze what you have.

A Note About Case Management Systems

Professor Gurvich also suggested, rightly, that a given firm or organization’s case management system will add information, likely a client ID and/or a matter number, to most documents. One thing that is great about case management systems is that they obscure the small details of document metadata and make things easier or more intuitive to find. In many ways, this is the point of software and information design — to make the user’s experience more fluid (and to prevent inconsistencies in data entry) so she need not worry about, say, following a complex system of filing naming perfectly.

The file-naming system described above is suggested for those without access to such a system, or those, like scholars, who use court documents in a way different from lawyers or judges. I’d suggest having a directory or file for each client, and a sub-directory for each matter, and then place named files inside, to roughly recreate the strength of a good automated document management system.

That said, I still think there is plenty of value in organizing one’s files according to a consistent scheme. This one is built with the idea of being both human and machine readable — that is, providing information to a user both at a glance and after some kind of software manipulation. Likewise, file names are indexed by all modern operating systems, meaning that using your computer’s search function will be faster, especially if you append descriptive phrases, such as party or document names, at the end of your file name.

And here, for your viewing pleasure, is a list of files of case documents:

Case Naming Conventions