Home » Commentary (Page 19)
Category Archives: Commentary
Public Domain Notices: A Good Idea?
In the course of my work of maintaining the Lost Docs Blog, I came across the following publication:
Substance Abuse and Mental Health Services Administration. After an [suicide] Attempt: A Guide for Taking Care of Yourself After Your Treatment in the Emergency Department. (SMA 08-4355; CMHS-SVP06-0157), Rockville, MD: Center for Mental Health Services, Substance Abuse and Mental Health Services Administration, U.S. Department of Health and Human Services, 2006. Reprinted 2009.I noticed it had this public domain notice that I've seen on some government publications:
Public Domain Notice All material appearing in this publication is in the public domain and may be reproduced or copied without permission from SAMHSA. Citation of the source is appreciated. This publication may not be reproduced or distributed for a fee without the specific, written authorization of the Office of Communications, SAMHSA, HHS.As a general rule, publications produced by the federal government are in the public domain and copyright free. There are exceptions that you can read about in our online library. It is a fact that not enough people realize the public domain nature of most government materials and so my reaction to this notice was initially very positive. I instinctively like the idea of labeling govdocs as public domain so that people and organizations (Google, I'm talking to you!) would feel free to reuse and remix without fear of consequences and not lock up content not meant to be locked up. On the other hand, if only a handful of agencies use such notices for public education, it is conceivable that an environment would be created where only govdocs with public domain notices would be treated as public domain. I'm not sure if that's a danger, but I worry. The possible danger would be less if a public domain notice was required governmentwide. What do you think? Are public domain notices on govdocs a good idea? Are they a good idea whether done governmentwide or by a few agencies? Would we be better off if there was a governmentwide policy to label the minority of copyrighted material in govdocs?
Note: Thanks to Vicki Tate for reporting this document to GPO and sending a copy of her receipt to the Lost Docs blog. Continue reading
The State of FDsys and the Future of the FDLP
The recent report on the state of the Government Printing Office's Federal Digital System (FDsys) should raise important questions for GPO and should be a wake up call for FDLP libraries. The report documents that the project is over budget, behind schedule, and lacks sufficient resources and planning to move forward successfully.
The report (Federal Digital System (FDsys) Independent Verification and Validation (IV&V) – Tenth Quarter Report on Risk Management, Issues, and Traceability Report Number 10-05, "IV&V Risk Management, Issues, And Traceability Report," January 14, 2010) was written by American Systems, under contract to the GPO Office of Inspector General and is attached to the following memo available from GPO:
- Federal Digital System (FDsys) Independent Verification And Validation – Tenth Quarter Report On Risk Management, Issues, And Traceability. Assessment Report 10-05, March 24, 2010.
The consultants were charged with assessing the state of FDsys implementation. Some of the findings of the report that will be of most interest to FDLP libraries are:
- FDsys as it exists today "bears only partial resemblance of the system that was envisioned."
- The program is significantly over budget. The original cost estimate for the first phase of FDsys implementation was $16 million. Through August 2009, GPO had spent more than twice that (approximately $33.6 million) and, by the end of FY 2010, the total costs for FDsys contractor support will be approximately $42 million.
- Even though the cost has more than doubled, the project is significantly behind schedule. "Release 1" of FDsys was slated to be accomplished in three phases ending in the Fall of 2009, but only the first phase has been deployed -- and even that phase is incomplete.
- GPO now says that only 42 Collections will be migrated to FDsys instead of the originally-planned 55.
- There is an on-going indexing problem within the FAST search product. The FDsys database was due to approach a critical threshold of 2.5 million records in December of 2009 and FAST will require changes to accomodate more records.
- The majority of the work on FDsys after the release of the first phase of Release 1 has been centered on fixing problems and dealing with emerging issues. GPO is focusing more on fixing and upgrading a deployed system than on building the final system.
- The FDsys Program has performed little to no analysis, planning, design, or development work for Release 2.
- The "large number [25] of deployments [production builds] over a ten month period reflects the obvious fact that the originally deployed system contained numerous deficiencies."
- The lack of clear definition of the system and the lack of a detailed implementation plan prevent GPO from determining realistic cost estimates for future development and endanger the ability of GPO to develop and deploy the final system.
- The consultants say that GPO does not have sufficient system engineering expertise to direct and oversee the development of FDsys and that this has resulted in a system with incomplete functionality, design problems, and numerous deficiencies. They recommend that GPO hire a senior system engineer and say that, without one, these problems will continue and future releases will likely take longer and cost more than anticipated. GPO management, however, completely disagrees with this recommendation.
There is more in the 38 page report, but the above gives you the gist of the problems.
The positive, the negative, and the risks.
There are some positive things. Much has been accomplished. Twenty-five of the most complex collections have been transferred from GPO Access to FDsys. The project managed to incorporate a significant design change during implementation to accomodate "Collections with numerous granules." The project also was able to create a new capability to support public access to FDsys information via the Data.gov website.
But these accomplishments are overshadowed by the numerous problems that the report documents. Even the already-deployed system is apparently overwhelmed with problems. The report documents 232 problems that adversely affect the accomplishment of an operational or mission-essential capability and notes that the many unresolved problems with the system create "a serious risk that the overall goals for FDsys ... will take much longer and require significantly more funding to achieve."
The failed "paradigm shift."
Since 1993, GPO has been championing a "paradigm shift" in responsibilities in which GPO arrogated to itself the responsibility for both access and preservation of government information and diminished the role of FDLP libraries. (See, for example, the discussion on GPO's draft regional libraries report and FGI comments.) We at FGI have been concerned about this shift from the beginning for a number of reasons. One of those reasons is the danger of entrusting all preservation and free access to any single organization. Any interruption or failure of that organization (financial, technological, political, etc.), could mean a catastrophic loss of access to government information for everyone.
We have been hopeful that interruptions would be small and short and failures would be in the future. But we have hoped to persuade the FDLP library community, including GPO, that it would be wiser and more prudent and more durable to build on the existing FDLP model of sharing responsibility for access and preservation across many institutions. These institutions with different infrastructures, governing bodies, technologies, and communities of users, would, we have argued, do a better job collectively than any one institution could do by itself.
We have feared the day when Congress would cut back GPO appropriations after we all were irreversibly dependent upon GPO -- a day when it would be too late to create a new system of free, permanent, public access to government information. With the release of this report, we worry that that day may be closer than we had imagined.
The original design and specifications for FDsys were expansive and ambitious. That was a good thing. It would be wonderful if GPO could support FDsys and all of its almost three thousand system requirements and features. OAIS compliance, persistent naming, metadata management, and support for RSS are among the features we look forward to. And we hope for other features: maybe, someday, APIs and OAI-PMH support, for example. But what do we do if GPO does not have the resources or the expertise to fully develop FDsys? It is hard to read this new report without being concerned that this is exactly the reality we face today. We worry that this report is "the writing on the wall" that is telling us that "the paradigm shift" will not work and is not sustainable.
Many FDLP libraries (or at least the directors of those libraries, and, in many cases, the FDLP librarians as well) have been hoping for almost two decades that they could rely on GPO to provide the services that the FDLP libraries themselves used to provide. If this is proving to be a false hope what will happen next? Is it only a matter of time before Congress pulls the plug, or GPO throws in the towel, or the private sector raises a stink?
What are our options for the future?
Naturally, we hope GPO can continue to develop FDsys. It would best for access and preservation to have FDsys in place. But it would be better if FDsys was not our only resource for preservation and access. It would be better if we had more systems in place to complement FDsys. It would be better if we had a digital FDLP that shared responsibility for access and preservation.
What options do we face right now? The obvious status-quo next step is for GPO to get more resources. It needs more money and more expertise so that it can deal with existing problems and move forward faster and with better planning that will make it easier for it to succeed and do so in a reasonable time frame and on budget.
But FDLP needs a "Plan B" to deal with the real possibility of GPO not getting adequate resources to finish or maintain FDsys. What will happen if we don't have a plan in place? We can imagine at least three generic scenarios: One, GPO will scale back and provide less access, or less secure preservation, or fewer collections, or some combination of those. Two, preservation and access will remain government-provided, but will become completely fee-based (somewhat like NTIS and STAT-USA). Three, the private sector will move in and demand, perhaps under OMB regulations, that GPO shouldn't have undertaken this job in the first place and that the government shouldn't provide a system that the private sector could provide. It would argue that raw information should be given to private sector companies who will produce their own preservation and access systems that will be fee-based. (We almost certainly will see a proposal to replace GPO's single-entity model with a private-sector, fee-based, single-entity model. Ithaka is already laying the groundwork for such a proposal. [See: Ithaka report on the future of the FDLP.] To those of us at FGI, this seems the worst of both worlds: relying again on a single organization rather than a community of organizations and moving that model to a fee-based system.)
There is also the possibility that none of these will happen and we will simply lose access because no one will take responsibility.
A better option; a more durable future.
But there is one other possibility: a collaborative effort in which GPO deposits digital files with FDLP libraries and those libraries preserve those files and make them accessible. This would be a real digital depository system with shared, distributed responsibility. It would have many advantages but, in the context of the current report, it has one major advantage over the current system: it has no single-point of failure (which is what we have with the GPO, single-entity, paradigm-shift model).
Such a system will take planning and resources and will not be trivial to implement. But the time to start planning for such a system is now. It would be much worse to wait until FDsys is in technological or budgetary crisis. At that point it could be too late.
Continue readingResponse to Public Printer
We at FGI would like to thank Robert C. Tapella, the Public Printer of the United States, for his response to our comments on his letter to President Obama regarding open government.
Mr. Tappella's response has some information that should be very encouraging and heartening to the depository library community. It also leaves some issues troublingly unaddressed.
Bulk Data Access to Legislative Information
First, it is wonderful to know that GPO is working with the Library of Congress, Congressional Research Service, the Law Library of Congress, and the Senate and House on the issue of access to bulk legislative data!
That news is important and significant. It is also very encouraging because it marks a new direction for dissemination of government information. Taken to its logical conclusion, this would mean that we will have a new route to obtaining government information. No longer will we be limited to information presented as web pages through government-built interfaces. No longer will we have to hope that web scraping will find all the information we want to gather or preserve. Raw information -- once locked in the dark web of government databases -- will be, potentially, available for libraries and others to download and repurpose.
Unfortunately, we can't look for this right away. Congress has only asked for a report, not action. The report itself is due "within 120 days of the release of Legislative Information System 2.0." Presumably that is a reference to a new version of the LIS that is currently only available within the legislative branch. I have not seen an announcement of a date for the release of a new version of the LIS, so it is not clear even when we can expect the report.
Nevertheless, it is certainly good to hear directly from Mr. Tapella that the task force working on this report will develop "a position on access to bulk data" and even intends to "work on making bulk data accessible."
It is somewhat ironic that this long, drawn-out process itself demonstrates the need for bulk data access. Although there have been calls for bulk data access for years, it literally took a legislative directive to get GPO and LOC and CRS to take the tentative steps they are taking now: to "develop a position" and "work on" the problem. Such passivity and long delays are, perhaps, inherent in a large, bureaucratic system, but they are crippling when it comes to keeping up with technological changes. This demonstrates why it is essential for the government to provide easy, free, reliable access to the raw information of government: doing so will enable others -- who can more quickly adopt new technologies -- to provide better access to that information faster than the government can.
What about Non-Legislative Data?
It is also unfortunate that the task force is only looking at bulk delivery of legislative information. Will it take another legislative directive to get GPO to "develop a position" on bulk access to other data? See Bulk Data Downloads: A Breakthrough in Government Transparency (by Tim O'Reilly, O'Reilly Radar, Mar 4, 2009) for a short list of other other data for which we need bulk access.
Will GPO Support Collections in FDLP Libraries or Just Backups?
Mr. Tapella's statement does not indicate that GPO has yet grasped the difference between 'backups' and digital deposit. GPO's focus is apparently still on making sure that its own collection is functional rather than facilitating digital collections in FDLP libraries. The "geographically dispersed content repository" described by Mr. Tapella is only "our backup" designed to ensure GPO's "continuity of operations" if GPO's own data repository becomes inoperable. This is a good and necessary feature but it is only a backup for GPO and has nothing to do with digital deposit.
Although Mr. Tapella points out that FDsys supports "repositories that can accept data much like libraries today accept tangible publications distributed from GPO," it seems clear that this generic design is intended as providing "backups" and would require "enhancements" to include bulk data access. This is a GPO-centric way of thinking. This is still a long way from GPO having a "position" on digital deposit and even further from "working on" making it possible.
Until GPO understands that it needs to support digital deposit so that FDLP libraries can build their own digital collections with their own functionality, FDLP libraries will not be partners in preservation and access; they will be, at best, little more than a backup for GPO.
APIs are not Digital Deposit
Mr. Tapella repeats the advantages of APIs, but fails to address the need for digital deposit. Providing APIs is not the same thing as providing digital deposit. As we have said in our original comment APIs are not magic. Each is a design for access and the product of choices made by the designer. Each has its own constraints built in. But don't take our word for it; read what developers say about the constraints of using existing government APIs:
- Extracting Government Spending Data via Talend and Ruby into CouchDB, by Rohit Amarnath, Full360 (04/11/2009).
- Improve databases, By Joshua Tauberer, The Hill (06/12/07).
We love APIs! We think they are great! We want more! We are so very glad that GPO will support them at last! But, please, Mr. Tapella, understand that APIs and a web site are only two of the three parts of a complete access system. Bulk data access is essential and we'd like to hear that GPO is planning for it now.
OAIS is not Digital Deposit
We are so very happy that FDsys is based on OAIS. It is something we have long advocated. But, again, Mr. Tapella, please understand that telling us about your preservation system and your intentions to preserve information does not reassure us that everything will be preserved and freely available to everyone forever. As we pointed out in our original comments, regardless of your intentions and the quality of your system, GPO may not always have the funding, resources, or mandate to provide free, permanent, public access to all government information and we therefore cannot rely on it alone to do so. And no single digital archive or repository can ever be as secure and safe as multiple archives. We need digital deposit to guarantee preservation and free access.
The GPO-centric approach to preservation and access is like a medieval town that stores all of its grain in one barn. When lightening strikes, the whole town goes hungry. In this day and age of $200 terabyte hard drives, peer-to-peer networks, and successful preservation systems like LOCKSS, it concerns us greatly that you still don't understand the need to have many collaborators working together to ensure long-term, free, public access.
Good News?
There are a couple of sentences in Mr. Tapella's reply that make me optimistic that GPO is on a path to change and does understand this need for collaborators. He says:
We need help from you and others in the community to help define future enhancements to access and data distribution. We see APIs as a one of the methods to provide advanced access tools, and realize that this is just one part of the ultimate solution.
To me, this says two important things: First, "data distribution" is on the GPO agenda, at least nominally; second, APIs are just one part of a bigger, ultimate, solution. This gives me hope for more. I hope I'm not reading too much into this.
See also:
- Bulk data and Legislative Information 2.0.
- Congress’ legislative information systems: THOMAS and the LIS by Jeffrey C. Griffith, Government Information Quarterly 18.1 (2001): 43-60. Apr 16, 2009
- Congressional Research Service Products: Taxpayers Should Have Easy Access, Project on Government Oversight, February 10, 2003.)
- Comparison of Legislative Resources on GPO Access and Selected Government and Non-Government Web Sites
- Remixes: Creative uses of free government information
- OpenHouse Project Op-Ed on Databases
Librarians without Libraries?
In his continuing series about Government Information Liberation, John Shuler considers the role of collections in libraries. One particularly revealing moment in his discussion is his day 60 post in which he describes a series of questions that he poses to his graduate students to get at the "fundamental things we do."
The Question and Conclusions
Can doctor still be a doctor without a hospital? They usually answer -- of course. Can you be a lawyer with out a courthouse? Again -- affirmative. Now the money shot -- Can you be a librarian without a library? Dead silence.
One would hope that the questions prompt a discussion and don't just end in "dead silence." Although John doesn't tell us what the discussion, if any, was, he does give us his conclusions: possession of "material" might have once been central to the purpose of libraries but, in the digital age, possession is much less important part of what libraries do.
Even though John qualifies his conclusions to allow for some limited role of collections for some libraries, he overwhelms his caveats with assertions that collections begin and end with the physical ownership of "material" and that "we will not own (possess) much of the material." He even coins the phrase "Gutenberg Librarians" to deprecate "possession and/or control" (66) of information by libraries.
So, John's essential, bottom-line conclusion, regardless of his caveats, comes across clearly: The net, John says, has brought on "the beginning of the end" of library collections (35).
I think his conclusion is wrong and the question he asks is misleading. You can see how misleading the question is by turning it around and realizing that the professions/institutions he uses are not parallel:
- Do doctors build hospitals? (No)
- Do lawyers build courthouses? (No)
- Do librarians build libraries? (Yes)
But the real problem is that the question implies a shared understanding of what a library is -- a shared understanding that I think we need to articulate explicitly. I think that, before one asks "Can you be a librarian without a library?" one should ask "What is the role of the library is in the digital age?" John has been outlining what he thinks the role of librarians should be and he apparently wants to separate the role of librarians from the role of libraries. Very well: let's examine the roles of both with some discussion, not dead silence.
Librarianship
I think John is implying is his series of posts that librarianship in the digital age will be about helping people navigate a complex, networked maze of shifting, changing information. Librarians will help users "connect the dots" and find connections that are not otherwise explicit (47). While there is nothing wrong with this view, and there is much to recommend it, it doesn't go far enough and it misses a key role for libraries.
As John portrays it, this view accepts that libraries will be less about selecting and preserving information and building digital collections and more about providing services for information over which librarians have no control. Librarians, in this view, are valuable precisely because they have no control over information.
This view accepts that information will be tightly controlled by producers and distributors. What is available, who can use it, under what conditions it may be used, and when it becomes no longer available will all be controlled by government agencies, publishers, individuals, organizations, and other "content" producers.
John also proposes that "librarianship" will be more important than "libraries." To me, this sounds like librarians will be analogous to travel agents who, because they deal every day with the complex, difficult, disparate, unconnected systems, are better able than the traveller to navigate these systems and find the best flight at the best price. So librarians, in this view, will help casual information users navigate a variety of complex, difficult, disparate, unconnected, public-freely-available and proprietary-and-licensed information systems. Just as travel agents have no control over what flights or trips are available or what they cost or what restrictions are placed on them, so librarians will have no control over what information is available or what it costs or what restrictions are placed on its use.
In this view, librarians will not manage collections but will license the right to read from those who control information. Whether the license comes in the form of payment of dollars to a commercial vendor and a written contract that licenses access, or an FDLP designation, or a contractual "partnership" with GPO, or the anointing of permission by Google Books legal department, the result is the same. As a recent article in Library Hi Tech says, "In future, librarians will no longer manage media, they will manage rights" (Böhner, Dörte. Digital rights description as part of digital rights management: a challenge for libraries. Library Hi Tech 26, no. 4 (2008): 598-605). This view reshapes the role of librarians from information providers to information gatekeepers; from information curators to business-officers who sign contracts and pay bills.
Who would want to go into that field?
Libraries
John hasn't said much about the role of libraries except to assert that, for many people, the digital environment is now the "default library" [emphasis added] that supports broad access to a "collection" of government information (51).
But, shouldn't we be asking about the future, not just describing the present?
Shouldn't we be asking about the relationships between doctors and lawyers and information? Certainly doctors and lawyers need a body of literature to practice their professions. Instead of asserting that users have access today, shouldn't we be asking, "Who will build and manage and preserve those collections and ensure long-term, free access to them?"
Shouldn't we be asking what guarantees we have that the information we want today will be available if we want it tomorrow? Shouldn't we be asking who controls access to that information and what are their reasons for providing access? Shouldn't we be asking who will pay for long-term preservation and access?
Just because users who are not familiar with information policy, information economics, or information technologies are happy with current access to information does not mean that they will be happy with the access (or lack of it!) tomorrow or in ten years or a hundred years. Providing easy access at one point in time does not guarantee easy access at a future point in time and can actually mask problems of long-term access.
It is one of the roles of librarians to think beyond today and one of the roles of libraries to guarantee access for tomorrow. We need to think about the long-term. Using short-term convenience as a reason for avoiding that kind of thought is evading one of the key roles of librarianship. And assuming that producers and distributors will have the same values and ethics and practices as librarians is to confuse the role of producers with the role of currators.
Maybe the real questions we should be asking are:
- Can lawyers practice without libraries?
- Can doctors practice without libraries?
- Can libraries exist without librarians?
The word "library" does not mean "I have some information." If it did, bookstores would be libraries and publishers would be librarians. We need libraries in addition to publishers and bookstores (and government agencies that distribute information as a by-product of another, primary, mission).
It is all about control
Let's be clear, then. Even in the paper and ink world, libraries and their collections were about wresting control of information from producers and distributors and granting control to local communities and information users. A publisher could take a book out of print, but a library could keep it available. A user could purchase a book and pay for magazine subscriptions, but could use the information for free at the library. Libraries leveraged economies of scale for the benefit of the community, enabling every community member to have benefits of access to information that no individual could possibly afford.
The need for wresting control of information away from those who wish to control the access to and the use of information has not changed in the digital world. But the battle lines have shifted and we need librarians in the fight to keep free, open, usable access.
"Content providers" want to replace copyright with license agreements. Producers want to charge for every single use and dictate who can use information, under what conditions, and in what way. Governments want to be able to alter and even withdraw information after it has been released. And the proliferation of requirements to register to read or use information portends a world in which people will not have the right of privacy when reading.
It is ironic that, given technologies that enable almost unlimited use and re-use of information and that enable information to be distributed and used and re-used almost without cost, we face a horde of stakeholders who want to limit access, charge for every use, restrict re-use, and look over your shoulder to see what you're reading.
More inaccurate conclusions
As noted above, John hedges his conclusion a bit. His wording is that "possession is much less exclusive or destiny for any one institution" and preserving and organizing the information sources "will remain important -- but is no longer our exclusive responsibility" (66). He expands on that idea:
- [G]overnments are taking back their possession of information sources. (60)
- [M]any other web sites [are] capturing the lost or deleted pages. (60)
And from these, he draws conclusions:
- [Information will] remain with the producers or be delivered directly to the users by the producers. (50)
- [W]e will not own (possess) much of the material we mediate on behalf of our user communities. (51)
- Possession ... is no longer a social good that is dominated [by] the dominion of libraries. (60)
To me, these summarize one possible scenario out of many. And, IMHO, this scenario is not one librarians should be content to accept or embrace. Why? Because it almost certainly guarantees that a lot of bad things will happen: loss of access, loss of free access, licensing constraints, DRM constraints, loss of information, loss of usability of information, and more.
Different Questions, A Different Answers
In a separate post, I will examine those issues in more detail, but I'll close this post with some assumptions and a couple of final rhetorical questions as a way of addressing John's question, "Can you be a librarian without a library?" The assumptions:
Society needs: organizations that select that information that deserves preserving from the plethora of information that surrounds us; organizations that then acquire, organize, and preserve that information; organizations that provide trusted, free, private, secure access to and service for that information. Society needs organizations that have the complete mix of all of these roles as their primary mission (not a secondary mission or a by-product of publishing, or dissemination, or making money). In the case of government information in a participatory democracy it is particularly important, even essential, that society has such organizations. Reliance on those who have some, but not all, of these roles will ensure that some of these roles will go unfulfilled. Reliance on organizations that have some or all of these roles as a secondary mission or by-product of another mission will endanger free access to information, preservation and integrity of information, and the privacy of readers, and will increase the risk of the loss of information.
The rhetorical questions:
- What would you call an organization that fulfills all the roles listed above but "The Library"?
- Why would libraries want to abandon these roles to organizations that do not have these roles as their primary mission?
- If libraries do abandon these roles, what is the risk that society will lose free, open, access to its essential information?
I think those questions lead us to conclusions that are very different from the the ones John reaches. I will examine this in more detail in another post.
Continue reading
Who Do You Serve and What Do You Do?: Defining Your Role to Ensure the Future of Our FDLP
October 7, 2010 / 2 Comments on Who Do You Serve and What Do You Do?: Defining Your Role to Ensure the Future of Our FDLP
The Defining Moment
As noted here recently, the depository community is into yet another round of trying to redefine the Federal Depository Library Program. (See: GPO contracts Ithaka S+R to develop sustainable FDLP models.)
This new project will question and evaluate the role that FDLP libraries will play in the lifecycle of government information. The definition of this role will determine whether or not FDLP libraries will deserve or get support from their constituencies. If they serve a useful function, they will get support; if they do not, they will not.
This is a defining moment. Libraries will not flourish or even survive because librarians like them, or because older people have fond memories of them, or even because we have a vague belief that they "should" survive. They will survive only if they fulfill a role in society that no one else fulfills as well -- or at all -- and if society recognizes and values that role.
Make no mistake about it: what is at stake is the survival of FDLP libraries. By defining the role of FDLP libraries, this project will determine whether or not there will be Federal Depository Libraries at all.
Defining the role of libraries
Typically, the roles of libraries are defined either in general terms of who the library serves or by enumerating specific tasks. You could call these the "who you serve" approach and the "what you do" approach. Each has advantages because each one can help focus our thinking and give us criteria against which we can evaluate our actions.
Since 1993, GPO has effectively defined a limited -- and shrinking -- role for FDLP libraries. The FDLP has always been a cooperative venture in which different partners (GPO, regional depositories, selective depositories) played different roles. But, since 1993, when The Government Printing Office Electronic Information Access Enhancement Act (Public Law 103-40) was passed, GPO has arrogated to itself the role of permanent preservation of government information and essentially prevented FDLP libraries from undertaking that role by refusing to deposit digital materials with depository libraries.
But that is changing. Recent developments (for example, GPO collaborating with LOCKSS in the LOCKSS-USDOCS project) have demonstrated that GPO is open to sharing responsibility, is no longer committed to preventing libraries from participating in digital preservation, is open to "digital deposit," and is, in general, open to new roles for FDLP libraries. These "new" roles could look a lot more like the traditional roles of FDLP libraries. Yes, we need to change the FDLP for the digital age, but these should not be changes in our traditional roles (what we do: build collections and provide services for and stewardship of those collections) but changes in procedures (how we do these things using digital tools instead of paper tools). It is in those traditional roles that libraries have a unique value in society. The Ithaka/GPO project will define the role of FDLP libraries either in a way that will expand this new openness, allowing libraries to have the flexibility to participate actively, or in a limited and passive way in the mode of the 1993-2009 model.
1. Who do you serve?
In defining the general role of libraries (who a library serves), there is a popular tendency to focus on the parent institution. This is an easy role to justify and explain and it even lends itself to some degree of quantification and accountability. The recent report from the Association of College and Research Libraries, The value of academic libraries: A Comprehensive Research Review and Report (by Megan Oakleaf, 2010) is a prime example of this view.
An alternative view is that libraries fulfill a larger role in society as a whole and thus serve more than their parent institution. The Darien Statements on the Library and Librarians (by John Blyberg, Kathryn Greenhill, and Cindi Trainor, 2009) is one recent example of this broader view of the role of libraries in society. Barbara Fister, a librarian at Gustavus Adolphus College, has written eloquently about this. New initiatives such as the NSF's rules for sharing of data and creating explicit plans for managing data for the long-term are driving libraries to anticipate a larger role for libraries in fulfilling the societal need for long-term stewardship and curation of information of all kinds across the life-cycle of information. We can anticipate this as a coming major shift in focus and priorities from the local to the global role of libraries.
While these two different views need not exclude each other, in practice they sometimes do. It would be wiser to view these two ideas as complementary rather than incompatible. I would argue, in fact, that any definition of the role of libraries that excludes one or the other of these views will almost certainly be incomplete and fatally flawed.
The role of FDLP as a whole vs. the role of individual FDLP libraries
I would expect that most people in the depository community would assume that the role of FDLP must, by its very nature and purpose, reflect a society-as-a-whole mission and go beyond the missions of individual participants in the program. It will be hard for Ithaka S+R to suggest a model that avoids the big, societal role of the FDLP. But the details of how to fulfill that societal role is the issue. What specific tasks will Ithaka S+R define for depository libraries, on the one hand, and GPO and other (unspecified) "partners" (RFQ, page 5), on the other hand? These definitions will either open up the options for libraries or explicitly limit them.
Despite broad statements of the role of the FDLP as a whole, such as "create an informed citizenry and an improved quality of life" (RFQ, page 4), I think we may see considerable pressure to use a narrow definition of the role of the individual depository libraries. One reason for this is the recent history of GPO and the FDLP in which GPO took over complete control of long-term preservation and access to all digital information in the program and relegated libraries to a role of only providing customer service. Some will see this split of roles as a de facto standard that should be continued. I would argue that, while that split may have seemed appropriate 17 years ago, much has changed and libraries are now more tech-savvy and better equipped to take on digital challenges. Those who argue for the 1993 status quo are the true luddites. It is a time for change.
The pressure to limit the role of libraries will come, I think, from librarians who view the role of their own library as limited to fulfilling the mission of their own institution -- those who would like someone else to take on the big, societal mission. It will come from those who support the Oakleaf ACRL report and its institution-focus and emphasis on "return-on-investment, commodity production, [and] impact." It will come from library directors who, for legitimate but parochial reasons, want to weed depository materials from their collections and do not wish to invest in digital depository collections. It may come from Ithaka S+R itself whose Manager of Research, Roger Schonfeld, has already praised the ACRL report because it "clearly frames the purpose and value of the academic library in the context of the parent organization." And, it may even come from some at GPO, since it matches the model GPO developed in 1993.
But there are those who will be advocating a broader, more active role for FDLP libraries. Those of us who believe that a network of Congressionally-mandated libraries can provide a better, more secure, more robust, more flexible, more responsive system than GPO or GPO and a few commercial "partners" could provide by themselves. One way to do this is to focus on the specific tasks that those libraries might undertake.
2. What do you do? The specific tasks.
There are a number of options for the tasks and roles of libraries. Many of these have been been well articulated and tried with varying degrees of success. For example:
Defining our own future
Over the past two decades GPO has redefined the role that FDLP libraries play in the lifecycle of government information by reducing that role to one of providing service for collections held by GPO and others. FDLP Libraries have largely accepted this de facto redefinition of their role. Why? Because they have been caught in a perfect storm of inadequate budgets and staffing and training, demands from library administrators to reduce the size and footprint of paper collections, users who were quick to accept online access without demanding -- or even being cognizant of -- long-term preservation, and a GPO that promised it would single-handedly take on the pesky problem of managing and preserving a single digital collection for everyone while simultaneously providing "access."
That model is failing and GPO is now open to a new model that involves depository libraries as active participants again. We have an opportunity with the Ithaka/GPO project to take the lead in defining the future of our own libraries. In the last two decades, depository libraries have followed the lead of GPO and accepted a diminished role of providing services without collections. We have followed the lead of technologists and digital-pundits who like to call the Google Books project a "library" while simultaneously diminishing the importance of actual libraries that are accountable to their communities. In a chicken-and-egg situation, our diminished activities have made depository activities easy targets for budget cuts that further diminished our ability to provide adequate digital services. As the private sector steps into this gap, our services begin to pale in comparison. We have not adequately differentiated ourselves from the private sector and government digital services, preferring to piggy back on what they do, enforce their rights-restrictions and their privacy-encroaching policies. But that strategy has endangered the principles of the FDLP and reduced our ability to do what the private sector will not and the government cannot do alone. Now we have an opportunity to change all that.
Where GPO must have a one-size-fits all collection and service model, FDLP libraries can each focus on their own communities of interest. Where private sector companies limit access to those who pay and GPO is specifically authorized in the 1993 law to "charge reasonable fees," FDLP libraries are dedicated to providing information without charging. While the private sector, by definition, provides only those services that generate a profit, FDLP libraries are funded to provide services for their communities by leveraging the resources of the community for the benefit of all. A GPO-centered model of preservation is fragile because it has only a single budgetary authority and a single, monolithic "community." In contrast, a preservation model based on FDLP libraries has as many as 1000 budgets, 1000 communities, 1000 locations, 1000 systems, and 1000 reasons to survive and flourish. It is 1000 times more secure.
FDLP libraries can build new digital collections that combine Title-44-materials with non-Title-44 materials. GPO cannot do that. We can support our own communities-of-interest that need no longer be geographically based. GPO has to serve everyone and does not have the resources to focus on every potential community of interest. We can build services and functionalities for our collections that focus on our communities of interest. GPO must provide generic services and generic APIs. We can guarantee that we will preserve the information in our collections for as long as those materials are of interest to our communities. GPO cannot guarantee that Congress will continue to fund preservation for everything forever. In fact, the RFQ does not contain the words "preservation" or "long-term." We can assure our communities that we will preserve their privacy and provide information that is usable and without fees. GPO cannot make those guarantees. We can, collectively, do a better, more secure job of preserving government information for the long-term and assuring that it will be available and usable without fees than any single institution or agency can. Together, we can build a twenty-first century FDLP that will do for digital materials what the FDLP has always done: ensure long-term, free, public access to government information.
It should be clear to us that returning to a model in which FDLP libraries take an active role in building and preserving collections and providing services will provide clear benefits to users of government information. But the benefits go beyond providing access and services. A strong FDLP also benefits the participating libraries, and other non-participating libraries. GPO and the Depository Library Council are working to create a comprehensive list of benefits for libraries participating in the FDLP and benefits afforded to the public by having access to these libraries.
Start today!
While the Ithaka/GPO project provides an opportunity to turn the FDLP around and make it viable and useful in the twenty-first century, it is not at all certain that this will happen. As noted above, there are those who will argue for the status quo that limits the role of FDLP libraries to an unsustainable, unjustifiable service-without-collections model.
Ithaka S+R has already written a report with a model for the FDLP (Documents for a Digital Democracy: A Model for the Federal Depository Library Program in the 21st Century). In that report, it recommended that "GPO should develop formal partnerships with a small number of dedicated preservation entities -- such as organizations like HathiTrust or Portico or individual libraries -- to preserve a copy of its materials" (page 44, emphasis added). As noted above, Ithaka S+R is affiliated with Portico through their parent organization, ITHAKA. (For another take on a related Ithaka S+R study, see: Nyquist, Corinne(2010) 'An Academic Librarian's Response to the “ITHAKA Faculty Survey 2009: Key Strategic Insights for Libraries, Publishers, and Societies”', Journal of Interlibrary Loan, Document Delivery & Electronic Reserve, 20: 4, 275 -- 280.) Although Roger Schonfeld has assured us that this time Ithaka S+R recommendations "will not focus on specific brands, services, or products, including those provided by any part of our organization," it appears that we will have to convince him and Ithaka S+R that FDLP libraries, not just a "small number of dedicated preservation entities" like Portico, must play a significant role in the preservation of FDLP library materials.
Ithaka S+R has pledged that their work will include broad, vigorous community engagement and that their work will will rely on community input and advice to guide their research and define their recommendations. It is time for us to speak up. Here are some things you can do today:
- Participate in the discussion on the project web site.
- Participate in FDLP's work to create a comprehensive list of benefits for libraries participating in the FDLP.
- Work with your colleagues to create a list of benefits to your own library of being an FDLP library. Share this with your library management.
- Identify your own library's user-communities. Do you have subject collections that are used by people beyond your local geographic community? Would those collections be enhanced if they included government-produced information? Make the case to your communities and your library management.
- Do you already have digital collections? Do you have digital collection tools that you could apply to government information? Or would you like to develop digital collections and services with copyright-free, DRM-free digital materials? Develop a plan that will enhance your library's digital future by utilizing free government information content.
- Add your comments and ideas here to this post on FGI.
Continue reading →Continue Reading →