Ze Frank tries to understand healthcare
Leave it to Ze Frank (many of you will remember Ze from "The Show", a daily video blog he did from March 17, 2006 - March 17, 2007), a comedian, to put this whole healthcare debate into proper perspective.
PACER and Crowdsourcing Court Records
Here is a first hand account by a user of court documents about why we need better access to court records than the 21 year old PACER system.
- Crowdsourcing Court Records, by Gautham Nagesh NextGov "Tech Insider" (08/31/09).
Last week I made a visit to the District of Columbia's federal courthouse to look up some documents for a story I've been working on. Since I don't have an account for the federal court records database known as PACER, heading down to the courthouse was the only way I could download and print the records I needed at a cost of eight cents per page. I sat down and dutifully printed out the first lengthy set of documents, only to find that somehow all of the text printed out backwards on the page. The second computer printed correctly, but proved slow and unresponsive. What I thought would be a a relatively straightforward task ended up consuming much of my afternoon. I was told users with accounts can access the records online, but even then the records are not searchable, making navigation time consuming and difficult.See also: Federal Courts Wary of Document-Sharing Plugin Recap Firefox Extension: "turning PACER around" Continue reading
Purls vs handles
Building on yesterday's post on Critical GPO systems and the FDLP cloud, I've done a little digging into GPO's proposed migration from [w:Purl]s to the use of "handles." According to RFP 3650 "Handle system overview,"
The Handle System includes an open protocol, a namespace, and a reference implementation of the protocol. The protocol enables a distributed computer system to store names, or handles, of digital resources and resolve those handles into the information necessary to locate, access, and otherwise make use of the resources. These associated values can be changed as needed to reflect the current state of the identified resource without changing the handle. This allows the name of the item to persist over changes of location and other current state information. Each handle may have its own administrator(s) and administration can be done in a distributed environment (my emphasis). The Handle System supports secured handle resolution. Security services such as data confidentiality, data integrity, and non-repudiation are provided upon client request.Purls and handles do roughly the same thing: they're link resolvers. But, as Larry Stone's 2000 article for MIT's Persistent Naming discovery project, "Competitive Evaluation of PURLs" points out, there are differences that make handles a better choice for long-term operation and persistence. Without getting too technical, handles are not connected to any protocol (i.e., [w:HTTP]) or domain (i.e., .gov) and can therefore work regardless of the network design or protocol used. This is extremely important for scalability and persistence over the long term. In addition, handles can do more than resolve to URLs. "The Handle System design allows for various other types of resolution objects, metadata, and extensible addtions to each Handle object record." In short, handles are more persistent, more scaleable, and can do more. But most importantly in my mind, handle administration, "can be done in a distributed environment." This makes handles perfect for the FDLP cloud because the work of resolving links can be done in a distributed environment. So I say, kudos to GPO for moving to the handle system. Oh, hold that applause for a moment. My search also turned up the following document from Fall 2007 Depository Library Council meeting entitled, "Handles Council Briefing Topic" (PDF). This briefing document basically describes what I've just said above and describes a gradual transition/migration from purls to handles with an anticipated timeline to, "coincide with Release 1-C of FDsys in 2008." There's a March, 6 2008 report, "Report on the handles beta test" that calls the handles beta test "satisfactory." But no information is available after that report. So what happened? I know the building of FDsys has been no easy task and that GPO staff have worked really hard to keep to their published release schedule; but I'd like to know why the handles migration didn't occur in 2008. If more testing is involved, I'm sure there are libraries that would be willing to be beta-beta testers for handles. Perhaps this is an opportune time to finally implement the migration to the handles system. --that is all. Continue reading
Comment on article: Depository Library Program in 2023
A recent article reports on a survey of ARL library directors and their vision of their libraries' roles in the depository library program:
- The Federal Depository Library Program in 2023: One Perspective on the Transition to the Future. Peter Hernon and Laura Saunders. College and Research Libraries, July 2009, Vol. 70, No. 4). [In the interest of academic discussion and openness, we've posted a copy of the article on FGI.]
The survey asked directors to choose among several future scenarios for the FDLP and their role of provision of government information. The authors are explicit about their intentions saying that "the study neither directly addresses whether the depository program itself will exist fifteen years hence nor offers a vision of what future will emerge after 2023." They also note that the survey explicitly focused on the question "how many libraries want to remain in the depository library program and what role do they intend to play?" This focus predetermines the outcome of the survey somewhat. It doesn't tell us what FDLP should be or how libraries could have a role in ensuring the long term, free access to government information. Instead we get a lot of information about what directors worry most about: money and resources.
The authors point out that no other study has systematically surveyed library directors for their perspective on the FDLP. This is particularly interesting given the rumors, gossip, and scuttlebutt going around about how many university librarians want to get rid of their depository collections, don't trust their depository librarians, and see depository status as costing more than it is worth.
The study reinforces some of those stereotypes and provides some evidence that some ARL library directors do indeed think that way. Sample quotes: "Several directors look forward to a time when they can 'dump the print.'" "Although some directors believe they have 'forward-thinking' documents librarians, others feel the opposite. As the director of a regional depository explains, 'the more that directors know about the program and a library's responsibilities, the less likely documents librarians can bluff about the legal obligations and seek to maintain the status quo.'" "The burden of participation in the program, including that of cost, is a recurring theme." "The directors I talk to all want to get rid of the [depository] collection and drop out of the program as soon as possible."
Not surprisingly, the directors who think that way are apparently part of the minority (13% that chose "scenario 1") who believe that libraries should withdraw from the depository program or that the program will simply wither away.
What the survey documents for the first time, however, is how much value ARL directors put in government information and digital collections. Many of the directors see government information as essential to their academic communities and have serious concerns about how to ensure its availability. Fully half the respondents envision (scenarios 3 and 4) some sort of digital collections as part of their responsibility -- either in partnership with GPO or separate from GPO if GPO does not provide adequate leadership.
While this survey is very interesting and provides much food for thought, it is far from the final word on the future of the FDLP, GPO, or government information. It leaves many questions unanswered and raises other questions. For example:
- The survey's use of the term "digital depository" is confusing at best and misleading at worst. One of the "scenarios" presented to directors in the survey describes "digital deposit" as the library providing "a digital feed of government information resources to its Web site, thereby becoming a portal for access to e-government information resources. The library receives, but does not create, digital content." We wonder how directors interpreted this? Did they think that "receiving" digital content meant getting copies of digital files that they would keep in a digital collection? Or did they think that "providing a feed" and "becoming a portal" was a passive job of pointing to content at GPO or elsewhere? The article does not make this clear and we would have to guess that directors may not have provided responses that we can interpret consistently. (And, we would have to ask the authors, whose work we respect, why they chose the outdated word, indeed the outdated concept, "portal"? Does anyone really believe that users want or will use "portals" anymore?)
- Another term that is used in a confusing way in the article (at least I was confused by it) is the term "dark archive." We normally associate this with digital archives such as Portico (which archives digital copies of journal articles but is "dark" because no one can see the articles unless a particular kind of event -- such as a publisher going out of business -- allows the archive to make articles available). In this article, the authors use "dark archive" in that sense but they also use it to refer to print collections that have copies of last resort. Was this confusing to the surveyed directors? Did different interpretations skew their answers?
- Some of this confusion is evidently apparent to the authors. When they analyzed the directors' comments, they discovered that there was some "imprecision" by directors in choosing a scenario. Some were unable to place their institution fully in one of the provided scenarios. There were many reasons for this, but it makes it harder for us to interpret and understand the results.
- The survey did not specifically present a scenario of real digital deposit in which GPO sends (i.e., deposits) authentic digital files to depository libraries. As noted above, the survey focused on two different but related questions: who wants to remain in the FDLP and what role do they intend to play. Combining those two questions may have further muddied the responses and left out options (e.g., true digital deposit).
- One theme mentioned several times in the article is the need for a shared digital archive of digitized materials similar to the JSTOR model. To me, this seems to be an indication that the directors value digital information, see a need for a trusted repository in addition to GPO, and would support shared responsibilities for such an archive. This should spark some good discussions at the next DLC meeting.
- The survey seems to perpetuate and even reinforce misleading concepts about the permanent availability of digital government information. Although the authors acknowledge that "government entities often do not retain all resources permanently on their homepages, and content can be difficult to find and can be subject to removal, redacting, or alteration", they also passively quote directors who say they will rely on search engines and other libraries and government web sites to provide government information for them. There are certainly some libraries (even among ARL libraries) that will not have large digital collections of government information, but the survey does an injustice by passing along these comments without follow up questions to those directors about who will ensure access.
- Another questionable idea that came out of the survey was about staffing. Several directors said "they would cease to employ separate, dedicated government documents librarians. They assume the specialized knowledge will be passed to reference librarians." Shouldn't ARL directors be thinking about the need for new skills to manage digital deposit and digital preservation and digital access to locally held files? Shouldn't they be concerned about the special skills that will be needed to locate government information and provide reference service for it if they do not have a collection that they control?
In summary, the article provides much to discuss and good opportunities for further research. It also provides some clear evidence that the rumors that ARL directors want to dump their depository collections and drop their depository status are well founded, but that these directors are in the minority. Most ARL directors highly value government information and are looking for smart, efficient ways to ensure long term access to digital collections.
Continue readingCritical GPO systems and the FDLP cloud
[Update: 10/13/09: I've revised my thinking on the cloud as the term is loaded and doesn't really mean what I'm describing. A friend from the San Diego Supercomputer Center said, "some greybeards are going back to the original metaphor: the grid" and suggested the term "shared digital libraries" which is good. But what I'm describing is more like a biological ecosystem, the FDLP ecosystem. jrj] Last week's GPO purl server crash should be disconcerting to both the documents community and the public at large (in fact, although the hardware's been restored, resolution is ongoing as I write). I know GPO staff are just as worried about this and are doing everything they can to fix the purl server.
"The PURL Server is currently inaccessible. GPO is working with IT staff to restore service as soon as possible. We regret any inconvenience caused by the server problems. An updated listserv will be sent once service is restored."But in the meantime, there are 1250+ library catalogs and innumerable links to government documents that are not working. The crash of a critical piece of GPO's infrastructure brings a couple of things to mind: 1) What worries me about this is that FDsys and it's supposed upgrade in hardware/software/systems design is for all intents and purposes the same as GPOaccess. That is, FDsys is a monolith where the failure of one piece can cause the whole system to ground to a halt. As our readers know, we've been advocating for a long time for a distributed digital FDLP (a *true* "digital depository" system!). We're heartened by what we see of FDsys so far, but we need to be building a system with built-in redundancies. I envision a collaborative and distributed system of digital content, collaborative cataloging/metadata creation, as well as technical infrastructure. With this kind of system in place, a failed purl server will only cause a momentary blip in service as a backup purl server kicks on instead of a several week+ outage. How many system degradations (WAIS) and failures (purl server) until we shift our thinking from "[w:client-server]" (with libraries decidedly on the "client" side of the equation) to "[w:Peer-to-peer]" concepts and build systems with built-in redundancies that mirror what the FDLP has been for the last 150 years? How long before we build an FDLP cloud?