Home » Commentary (Page 16)
Category Archives: Commentary
Privatization of GPO, Defunding of FDsys, and the Future of the FDLP
On July 22, the House passed a bill that would remove funding for FDsys, reduce funding for GPO by 20%, and reduce funding for the Superintendent of Documents by 16% (Kelley). The House Report on the bill also directs the Government Accountability Office to conduct a study on "the privatization of the GPO" and the transfer of the Superintendent of Documents and the FDLP to the Library of Congress (page 25).
The bill includes many other changes that are relevant to the dissemination of government information (see House Bill Questions Future of GPO and the comments to that post, and the stories in Library Journal and OMB Watch), but the ones related to FDsys and the privatization of the GPO are the ones which, if ultimately approved, would have the greatest negative impact on long-term free public access to government information.
Passage of only some of these bad ideas would almost certainly result in a catastrophic loss of long-term access to and preservation of government information. These bad ideas are, however, only symptoms of a still bigger problem. There is, luckily, an obvious, logical path around all these threats.
Proposals not new
While these proposed cuts and changes are drastic, they are not new. Similar proposals were considered in 1982 and 2001 by NCLIS, in 1988 by the Office of Technology Assessment, and in 1993 and 1994 by bills in the House of Representatives.
In addition to these official recommendations, the information industry has long argued that the private sector, not government agencies, should disseminate government information. It has characterized almost any government information activity as unfair competition with the private sector. Industry commissioned reports and official statements in 2000 and 2004 (Wasch) suggested that governments should only distribute raw data and should refrain from making data easier to use if there is even a potential commercial market for such information.
These private sector ideas have re-emerged in the last few years as governments have made raw data more easily accessible and technological mashups of government data have become almost commonplace. Calls for government to limit its role to the delivery of raw data and for a reliance on the private sector to make the data useful have become popular. (Robinson)
Bad Policies
Whether such proposals suggest turning over government information dissemination to the private sector or commercializing the distribution of information by agencies themselves, when such proposals have been examined from the perspective of the user and from the perspective of information access in a democracy, they have been found to be severely wanting.
An examination of the literature reveals three reasons that proposals to privatize and commercialize government information make bad policy. First, by commoditizing public information, they conflict with the needs by citizens in a democracy for free access to accurate information about the activities of government. Second, they ignore that producing and disseminating public information is an essential role of government, not something that can be left to the whims of the market. Third, it has never been demonstrated that the privatization of major federal information dissemination activities is cost-effective or beneficial for important governmental functions.
It is also worth remembering that GPO was originally created because relying on private printing did not work well. Private printers often delivered jobs late and the printers themselves found that they lost money on public printing contracts (MacGilvray). Today, GPO contracts with many private publishers while maintaining overall control of the entire throughput.
Even information-industry-friendly reports on similar proposals have recognized an important, even essential, role for the government in government information dissemination. The 1982 NCLIS report, while strongly promoting a major role for the private-sector, nevertheless said that government information should be openly available without any constraints on subsequent use. It also advocated depositing documents into FDLP libraries for free accessibility. The 2001 NCLIS report similarly supported private-sector involvement but also concluded that, "...the federal government must continue to have primary responsibility for the entire life cycle of government information, including the dissemination and permanent public availability to public information resources to the American public without restrictions on its use or reuse." (emphasis added)
Nevertheless, there are still those who promote policies that would rely on market forces to determine what public information would be available to the public and at what cost.
Strong opposition to that approach comes from non-profits, libraries, citizen advocacy groups, scientists, journalists, historians, and government agencies. These groups understand that "there is [a] need to ensure equitable, open access by the public in general to information which has been generated, collected, processed, and/or distributed with taxpayer funds." (NCLIS p.ix). And in 1988, OTA said, some government information dissemination activities are "inherently governmental" because they "facilitate an informed citizenry [and] assist the mission agencies in carrying out their statutory responsibilities." (p301)
Failed Attempts
Some attempts by the government to commercialize or commoditize its information have failed either economically or functionally. For example, although STAT-USA existed on a "revolving fund" without Congressional funding for many years, charging a cost recovery fee for access to economic and trade information from federal agencies, in the long run it found that its fee-for-service business model was no longer viable and it shut down its operations. (Krasowska)
If you have been around government information issues for less than fifteen years, you may not be aware that the first incarnation of GPO Access attempted a cost recovery model similar to NTIS or STAT-USA. It charged annual suscription fees ranging from hundreds to thousands of dollars for access to the Congressional Record and Federal Register (GPO Access Status Report ). This model failed and was abandoned after less than two years (Relyea), partly as a result of libraries creating gateways that made this same information available without charge.
Even when fee-based services, such as PACER (Public Access to Court Electronic Records), seem to survive financially, their functional failure to provide free information is obvious and it is arguably true that they fail to adequately meet the needs of all.
Catch 22
There are Catch-22s implicit in proposals to privatize or commercialize government information. First, the information-industry suggests that it should have exclusive rights to information products that are profitable and leave to governments those that are not profitable. This sets up governments for failure when they try to support their activities with income from demonstrably non-profitable information products.
Second, governments set themselves up for failure when they charge for access to public information. If they simultaneously attempt to honor their role of providing information to the public without charge while charging for that same information (as in the early years of GPO Access), they compete against themselves. But if they attempt to protect their ability to charge for their information "products," they find themselves in the awkward position of attempting to control and restrict access to public information that is in the public domain. (Gellman)
Ultimately, attempts to commercialize government information therefore conflict fundamentally with the essential and inherent duty of government to make public information freely available and usable.
The current threat
Unfortunately, just because a proposal is bad policy, self-contradictory, or doomed to failure does not keep it from being implemented. The current budgetary and political situations in Washington DC create an environment where one or more of these bad ideas is more likely to pass than ever before.
Regardless of how important this issue is, it is unlikely that it will get much media attention. It is also not at all clear that proposals to keep government information free and well-preserved will garner much support politically. When essential government services such as food safety, police, defense, nutritional programs for low-income women and children, nurses, clean drinking water, and much more all face drastic cuts, will there even be room in the budget debates to consider government information? When Congress can seriously consider proposals to cut spending on programs that affect the health and safety of the country, we can hardly assume that it will necessarily provide adequate funding for information access. President Obama's own government transparency programs have been drastically cut and Obama himself is on record as thinking the printing of the Federal Register is wasteful.
The Big Problems
As serious as the current situation is, it can at least help us see the bigger issues that surround long-term preservation and access of government information and suggest solutions. The big problem is that we lack an adequate preservation and access "ecosystem" for government information. This puts all government information at the mercy of relatively small changes in government budgets. It is somewhat ironic that, if we had addressed the underlying issues earlier and had a rich ecosystem, we would be less vulnerable to the drastic proposals on the table today.
There are lots of issues and challenges that face those who wish to preserve long-term free access to government information. We can boil down a lot of those issues to two big ones:
1. Quantity. Just the quantity of information being produced digitally provides one huge challenge. Any attempt to preserve so much information must be able to scale to sizes that, until recently, were almost unimaginable. As Nicholas Taylor at the Library of Congress wrote recently, the amount of "data stored by the Library of Congress" has become a popular, if unusual, unit of measurement for capacity of storage, network traffic speed, size of digital collections, and so forth. The "End of Term" crawl of the web pages of the George W. Bush presidential administration by the Library of Congress, the California Digital Library, the University of North Texas, the Internet Archive, and the Government Printing Office produced almost 16 terabytes of data. (See more size comparisons here.) And digital preservation and access requires duplication and replication and backups that multiply the scale of projects quickly. LOCKSS-USDOCS, for example, says that the approximately 1 terabyte of data it is currently preserving is only a fraction of the 18 terabytes of content in FDSy when all the workflow iterations, copies, and backups are taken into account.
What this means is that providing preservation and access to all government information is a very large, non-trivial task. It is not clear that any one institution or organization will ever have the capacity or resources to do everything on its own.
2. Selection. But, you may well ask, how much of all digital government information is worth preserving? It is almost certainly true that much of the born digital content being produced by the government is of only transient interest or value. It is without question true that the rules have changed in ways that make it more difficult to know what is worth saving. In the past, we knew and could fairly easily define and identify "government publications" and could identify who created and published them. "Publications" were, for the most part, packaged as "books" and "journals" and "pamphlets" and so forth. These qualities made it relatively easy to know what we wanted to preserve and how to preserve it.
But in the digital environment, we find ourselves facing a whole new set of circumstances. It is not always clear who has created digital information, whether or not it is "government" information, or whether or not we have sufficient rights to collect or preserve or provide access to any given piece of information (Peterson). A single web page may display information from many different sources. A dot-gov web page may contain information from a commercial source and government agencies may post original content on dot-com web sites. The very processes that put a wealth of government information a click or two away also make it harder for us to preserve that same information and ensure its usability far into the future.
Apart from some obvious, preeminent series (e.g., Federal Register, Congressional Record, Hearings, Reports, the censuses, and other Essential Titles), lies everything else. Who will decide what of that "everything else" is worth saving? Who will decide if we save the digital equivalent of looseleaf binders, pamphlets, posters, one-off maps, slip laws, drafts, versions, editions, memos, press releases, and so forth? We must consider multi-media formats. We have to decide whether or not the "look and feel" of website presentations of information is important to preserve and, when there are several different presentations of the same information, which we should preserve.
Selection in the world of bad budgets ultimately means de-selection and weeding. Digital objects don't get preserved by accident. They require constant attention and preservation work. When a repository says, "We can no longer afford to preserve this and this and this," it is often relegating those things to oblivion.
Despite these big difference between the digital world and the analog world, the big, foundational issues we face are not that different. Specifically, there are two foundational issues: First, different people have different needs. What is important to you may not be important to me and vice versa. Second, the question of selection of what to preserve is a question of who will have the decision making power and who will have the control over their own decisions (Jacobs).
Some conclusions. There are some inescapable conclusions we can draw from the combination of the issue of quantity and need for selection. First, there is a need for more than one organization to be responsible for preservation and long-term access just to deal with quantity and scale. We cannot rely on any single institution or organization to preserve everything that is of value to everyone; that is just too big a job. The Library of Congress has come to the same conclusion, which is why it has created the National Digital Stewardship Alliance (NDSA).
Second, there is a need for different organizations to be involved in preservation in order to adequately reflect the information needs of different user communities. No single institution that intends to serve "everyone" can afford (literally afford, in terms of money and other resources) to pay sufficient attention to the needs of every small, specialized constituency. Without such attention, information will fall through the cracks and be lost.
Third, each such institution must have the ability to select information for preservation and obtain sufficient control over that information such that it can perform the needed digital preservation activities that will ensure long-term preservation of and access to that information.
Digital Preservation Road Maps
Luckily, we have road maps for digital preservation that help us address the issues and challenges outlined above. The road maps are the Reference Model for an Open Archival Information System (OAIS) combined with the checklist for certifying digital repositories, the Audit And Certification Of Trustworthy Digital Repositories (TDR).
TDR is built upon OAIS. Together they provide the context for long-term preservation and access to any digital collection. They do not describe how to build a repository nor do they define technologies that must be used. Rather, OAIS describes the required functions of a digital repository and TDR provides a checklist of "metrics" for evaluating if a given repository is meeting its own goals and objectives for achieving those functions. OAIS and TDR are just as applicable to small repositories and institutions as large ones.
TDR recognizes that preservation is not just about technology. It is also about continuity over time of the archive itself. TDR describes two essential requirements in this area that are particularly relevant here: the need for long-term financial sustainability and the need for succession planning.
1. Sustainability. TDR says that, to ensure viability, a repository must have business planning processes that ensure its financial sustainability over time.
Viewing sustainability for government agencies is tricky. On the one hand, an agency can claim that it has the full faith and credit of the government, legal mandates, and (in some cases) the historical precedent of its long-term mission. On the other hand, agencies come and go, budgets are cut and reallocated, and missions change.
In fact, as noted above, the current proposals are only the most recent examples of these very issues facing GPO. GPO has always had high hopes and made big promises, but its hopes and promises are limited by what Congress sets as its mission from year to year and how Congress funds it -- or denies it funding. In a single budget cycle, "permanent preservation" can change to "temporary storage" and "free" can change to "fee-based." A single bad-budget year can force GPO to make selection decisions that result in weeding of information that some communities will still consider vital.
While a lot of what affects sustainability is outside the control of the repository, there are many things than each repository can control and many actions it can take to control those. It can also take actions that will provide the best possible context for dealing with events outside its control. TDR enumerates these. But TDR says that a repository must also prepare for the possibility that unforeseen or unavoidable events might make sustainability impossible. For such occasions, a repository needs a succession plan.
2. Succession Planning. Any organization faces the possibility of funding cuts and shortages and unforeseen problems that can result in anything from scaling back to going out of existence entirely. IBM recently made this point clear about private sector companies when it said, "Nearly all the companies our grandparents admired have disappeared. Of the top 25 industrial corporations in the United States in 1900, only two remained on that list at the start of the 1960s. And of the top 25 companies on the Fortune 500 in 1961, only six remain there today." TDR recognizes this and says that any trusted repository must have a formal succession plan, contingency plans, or escrow arrangements in case the repository ceases to operate or the governing or funding institution substantially changes its scope. These are exactly the threats GPO faces today. I cannot think of a better demonstration of the need for succession planning.
But what does it mean to have a succession plan? It means having a plan that will ensure the long-term preservation of the content for which a repository is responsible even if the repository ceases to exist. In general terms, it means that an organization has a plan for what specific actions it will take if it learns it has to change missions or if it will cease to exist. In extreme circumstances, it means that it has a plan in place to hand over its content to one or more trusted repositories.
We already have some existing projects for government information that may serve as models for for viable, long-term, collaborative solutions to succession. These include the Department of State Foreign Affairs Network (DOSFAN) partnership between the U.S. Department of State, the University of Illinois at Chicago, and the Government Printing Office; the LOCKSS-USDOCS partnership between Stanford, Carl Malamud's public.resource.org, GPO's FDsys, and more than three dozen libaries; and the CyberCemetery partnership between The University of North Texas Libraries and GPO.
In order for a repository to say that its content will survive the downsizing or elimination of the repository, it needs to be able to show that its content already is in another repository or that it could hand over its content to another repository. For a hand-over to take place, there would have to be another repository technically capable of accepting such a hand-over.
This, along with the above conclusions based on quantity and selection, leads us to some solutions both for our current situation as well as for the underlying issues surrounding long-term preservation and access.
Solutions
There is a common theme to the conclusions above. First, to ensure preservation of all that needs to be preserved, we need multiple repositories serving the needs of multiple communities of interest. OAIS calls these "Designated Communities" and both OAIS and TDR make them an essential (non-optional) element of trusted repositories.
Second, in order for repositories to have realistic succession plans, we need an information preservation ecosystem consisting of many repositories capable of cooperating with each other's succession planning.
In a nutshell: The more repositories we have, the more secure all repositories will be, collectively. The more repositories we have, the better we can ensure that content relevant to all user communities will be selected and preserved by at least one of those repositories.
Visions of the future
What might this look like in practice? There is no single prescription for success, but we can imagine effective, practical, successful scenarios. Success would be achieved if we had a mix of a variety of different kinds of libraries and archives and repositories, each working for the best interests of its own designated user community, but, collectively, providing a national, loosely-coupled "system" of preservation and access. (Does this sound like the traditional FDLP? Yes! The FDLP provides us with a working model of experience in just such a system.)
In such a system, individual libraries (small and large) and consortia of libraries (small and large) could contribute to the long-term free public access to government information -- simply by meeting the needs of their own user communities.
The Digital Public Library of America might provide a technical and organizational framework within which many libraries might act and contribute.
I can imagine lots of examples of how individual libraries or groups of libraries might take actions that would benefit their own user communities as well as the information ecosystem as a whole. I am sure that you can add to this list from your own experiences with your own user communities.
- A few big repositories like HathiTrust, the Internet Archive, and LOCKSS-USDOCS containing large volumes of easily identifiable and obtainable major series of government digital information.
- Consortia of law libraries (like the Chesapeake Project Legal Information Archive) combining forces to preserve the basic, essential, official legal record of the nation (from all 3 branches).
- Regional, state, and local law libraries preserving local jurisdictional legal information and linking their collections through rich metadata and APIs to each other and national collections.
- Libraries with a regional focus collecting information relevant to the region from multiple agencies and jurisdictions. (e.g. water rights, immigration, trade, agriculture)
- Libraries that focus on specific kinds of users with common kinds of information needs (e.g., undergraduates, K-12, practicing physicians, farmers) collecting government information from many sources to build strong, dynamic working collections.
- Libraries that want to emphasize a particular kind of information or research (e.g., spatial/GIS data, astronomical data, statistical and raw numeric data from censuses, weather data, textual corpa), combining government information with information from other sources and with computational tools to provide rich research environments for researchers.
- Research libraries with institutional repositories of their research output combining government information to supplement, document, and enhance those collections.
The above are just examples, not prescriptions or predictions. The concept I want to illustrate above is that, when lots of libraries and archives and repositories select and acquire digital government information and create rich digital collections for their own communities, the result will be, collectively, better preservation and more focused access than any single institution could create on its own. This rich environment would be much more secure than our current environment in which each library hopes that some other library or government agency will take care of preservation and access to materials that are essential to its own user community.
Next Steps
So what do we do next?
- We need to oppose recommendations before Congress that would gut GPO or force GPO to weed or disable FDsys or commercialize government information. The current bill will not be the last; we need to be able to make a convincing, persuasive case that government has an essential, inherent role in the life cycle of government information.
- We need to work with existing large digital repositories (e.g. HathiTrust, Internet Archive, LOCKSS-USDOCS, etc.) to see if they can host government information and make it freely accessible now -- particularly in the event of a scaled back or discontinued FDsys.
- We need to work with Depository Library Council, GODORT, ALA, GPO, our own local FDLP libraries and Regional Depositories to plan for an FDLP of the future that includes life-cycle management of digital government information. This will inevitably include, but not be limited to, digital deposit of Title 44 materials into FDLP libraries.
- We need to instruct ourselves in the requirements of Trusted Digital Repositories by learning about OAIS and TDR. Where there are learning opportunities we need to take them and where there need to be new opportunities we need to make them. Those of us with influence on the curricula of library schools need to make this a requirement.
- Building on our own individual knowledge we can then work at a local level within our own libraries and library consortia and library organizations to build our own digital infrastructures and digital collections that meet the requirements of OAIS and TDR. We need to make sure that the planning process is not overwhelmed by technical considerations to the exclusion of long-term sustainability and succession planning. Sustainability and succession planning need to be integrated into the planning process from the beginning, not addressed later as an afterthought. This will help us have better conversations with our colleagues and will lead to more cooperative projects and better cooperative planning.
- We need to work with national and regional organizations and professional associations to plan for a future information preservation ecosystem and infrastructure. Librarians need to work with different kinds of libraries; librarians and archivists and technologists need to work together. The ecosystem doesn't have to be a huge bureaucratic institution -- indeed, it probably should not be -- but it will benefit from collaborations and planning that stretch across traditional boundaries.
Ask or Act?
The future of long-term preservation of and free access to government information is in the hands of Congress today. That leaves us with the feeling that all we can do is ask Congress to do the right thing. But we can do more than ask; we can act. Indeed, we must act. We have the power to take that control out of the hands of Congress and put it into our own hands by building our own digital collections. For many libraries, that will mean a change in strategy: instead of relying on someone else to ensure long-term access to the information your Designated Community requires, you will rely on your own actions. This comes with costs, of course, but it also has big benefits. You will be providing the essential services that your community needs. And that means that you will have a built-in, inherent role that no one else has, which will make your library more sustainable for the long run.
Endnotes.
- Ambacher, Bruce I., Government Archives and the Digital Repository Audit Checklist, Journal of Digital Information, 8 (2007).
- Consultative Committee for Space Data Systems, Reference Model for an Open Archival Information System (OAIS) CCSDS 650.0-B-1 BLUE BOOK January 2002’ (CCSDS Secretariat, 2002), CCDS.
- Consultative Committee for Space Data Systems, Audit And Certification Of Trustworthy Digital Repositories, "Red Book," Issue 1 (Washington D.C.: Council of the Consultative Committee for Space Data Systems, October 2009).
- Federal Executive Agencies Terminated, Transferred, or Changed in Name Subsequent to March 4, 1933, United States Government Manual 2009-2010 (Appendix B).
- Gellman, Robert M. Twin Evils: Government Copyright And Copyright-Like Controls Over Government Information, Syracuse Law Review 45:999 (1995).
- Government Printing Office Electronic Information Access Enhancement Act of 1993 [Public Law 103-40].
- House Report 112-148, to accompany H.R. 2551, Legislative Branch Appropriations Bill, 2012, Committee on Appropriations (July 15, 2011)
- H.R.2551, Legislative Branch Appropriations Act, 2012, Referred to Senate committee 7/22/2011.
- Jacobs, James A. FDLP: Services and Collections [preprint] by Against the Grain, 21(2) April/May 2009.
- Kelley, Michael. Bill Passed by House Would Provide No Money for GPO's Federal Digital System, Sharply Cuts Other Information Resources, Library Journal (Jul 27, 2011).
- Krasowska, Francine. A Message from STAT-USA’s Director (August 2010)
- MacGilvray, Daniel R. A Short History of GPO, Administrative Notes (1986).
- McGilvray, Jessica. ALA opposes cuts to Government Printing Office in Legislative Branch Appropriations Act, by District Dispatch, American Library Association, Washington Office (July 21, 2011).
- OMB Watch. House Questions Future of Government Printing Office, (July 27, 2011)
- Peterson, Karrie and Jacobs, James A. Government Information in the Digital Era: Free Culture or Controlled Substance?, paper presented at the symposium, "Free Culture and the Digital Library" at Emory University in Atlanta Georgia, October 2005.
- Relyea, Harold C. Public Printing Reform: Issues and Actions, Congressional Research Services report 98-687 (June 17, 2003),
- Robinson, David G., Yu, Harlan, Zeller, William P. and Felten, Edward W., Government Data and the Invisible Hand (2009). Yale Journal of Law & Technology, Vol. 11, p. 160, 2009.
- Sheketoff, Emily. Letter [MS Word document; available as a PDF document here] to Harold Rogers and Norman D. Dicks, Committee on Appropriations U.S. House of Representatives, from Emily Sheketoff, Executive Director ALA Washington Office (July 21, 2011). [includes attached "Resolution On Government Printing Office Fy 2012 Appropriations" Adopted by the Council of the American Library Association, June 28, 2011.
- STAT-USA. STAT-USA Office to Cease Operations September 30, 2010
- Stiglitz, Joseph E., Orszag, Peter R., and Orszag, Jonathan M. The Role of Government in a Digital Age, Commissioned by the Computer & Communications Industry Association. October 2000.
- Terry, Jenni. House passes Legislative Branch Appropriations Act with 20 percent cut to Government Printing Office, District Dispatch, American Library Association, Washington Office (July 25, 2011).
- U.S. Congress, Office of Technology Assessment, Informing the Nation: Federal Information Dissemination in an Electronic Age, OTA-C IT-396 (Washington, DC: U.S. Government Printing Office, October 1988). [Y 3.T 22/2:In 3/9:]
- U.S. General Accounting Office. Information Management: Electronic Dissemination of Government Publications, GAO Report 01-428 (March 30, 2001)
- U.S. Government Printing Office. Essential Titles for Public Use in Paper or Other Tangible Format. (Written on Monday, 24 November 2008 Last Updated on Monday, 20 June 2011)
- U.S. Government Printing Office. GPO Access: Status Report. (June 30, 1994).
- U.S. Government Printing Office. Printing Procurement Regulations (revised 2/11)
- U.S. National Commission on Libraries and Information Science. A comprehensive assessment of public information dissemination: final report, United States. National Commission on Libraries and Information Science, Washington, DC : The Commission, (2001) [Y 3.L 61:2 D 63].
- U.S. National Commission on Libraries and Information Science. Public Sector/Private Sector Interaction in Providing Information Services. Report to the NCLIS from the Public Sector/Private Sector Task Force. U.S. Government Printing Office, Washington, DC (1982). [Y 3.L 61:2 P 96/2].
- U.S. Office of Management and Budet. OMB Circular A-130, Transmittal Memorandum #4, Management of Federal Information Resources (11/28/2000)
- Wasch, Ken. Letter (May 13, 2004) "SIIA Comments Regarding New Economic Model for The GPO Sales Program," Letter to Bruce James, Public Printer, U.S. Government Printing Office from From Ken Wasch, President Software and Industry Information Association.
Promises, Promises…
Following up on yesterday's post about Another Google Search going away: Gary Price notes that Google had promised an archive of Twitter posts and that Google has recently removed another service:
- Google Realtime Search Offline; It Will Return But What About Complete Twitter Archive Google Was Planning?, by Gary D. Price, INFOdocket (July 4, 2011).
- Official: The Google Wonder Wheel Is Gone, by Gary Price, Search Engine Land (Jul 3, 2011).
Nearly all the companies our grandparents admired have disappeared. Of the top 25 industrial corporations in the United States in 1900, only two remained on that list at the start of the 1960s. And of the top 25 companies on the Fortune 500 in 1961, only six remain there today. -- How does an organization outlive its founder?, by marty kelly, IBM Smart Camp blog (June 16, 2011).This isn't surprising. What is profitable comes and goes. What is important for a user community shouldn't be left to the whims of the marketplace; it should be in control of the community through its own institutions. When we consider the information that is important to a user community, that institution is, by definition, the library. Then promises can be made by -- and kept by -- the community itself. Continue reading
E-Gov: are we citizens or customers?
The idea of E-government initiatives is to make it easier for citizens to transact their business with their governments. This is surely a good idea, but it carries with it several problems including endangering the long term preservation of government information.
Take, for example, Adobe's new product, The Adobe Digital Enterprise Platform for Customer Experience Management (CEM), which it hopes will attract government agencies:
- New Adobe platform would personalize an agency website for individual users, by Joseph Marks, NextGov (06/20/2011). A new Adobe product unveiled Monday would allow a federal agency to tailor its website and customer service operations to specific citizens based on their geographic location and, perhaps, their past contact with the agency.
This sounds attractive in a lot of ways. It promises better customer service, personalized information, and faster access to relevant information.
There are, however, several problems if this approach is used exclusively.
Citizens or Customers?
Adobe says that its software allows agencies to "stop making a distinction between customers and citizens." Surely all of us would like to know that our "customer experience" with the DMV would be as easy and straightforward (and brief!) as our experiences with the best commercial web sites. Companies like Amazon have made their fortunes not because they offer better products, but because they make it easier to find and buy those products. Wouldn't it be nice to have have government agencies' web sites work as well as the best commercial web sites? Wouldn't it be great if government agencies could shrug off the old, cliched unfriendly-to-users image, and create new, user-friendly, customer-centered web sites?
It would, of course. But the problem is that, when we visit an agency web site, we are not always the "customer" of that agency. We are more often citizens seeking information than we are customers engaging in business-like transactions.
And that is the beginning of the problem. Treating citizens as customers can jeopardize our privacy, make it harder for us to find the information we want, and make it harder to preserve government information for the future.
Privacy. There are, of course, big privacy issues if governments start replacing the dissemination of information with the personalized transactions of e-government. Citizens should be able to search, browse for, read, and use government information without the government tracking and recording each individual's every search and use. The e-gov interaction between citizen and agency requires just such tracking, however. Adobe, for example, says of its product that it would provide "an instant, unified record of a customer's interaction with a company or agency, regardless of where or how that interaction is happening."
There are certainly occasions when citizens want and need to personally interact with a government, but we probably all hope that we don't have to do this frequently. Going to the DMV to renew a license, or applying for a grant, or filing tax returns are not what we do (or want to do!) every day. These are the exceptions to our interactions with governments.
Most of our interactions with governments are about looking for information that the government has gathered, or compiled, or created as part of its mission. Whether it is about proposed legislation, or existing regulations, or the location of flood-plains, or the population of a city, or the latest economic indicators, or how to manage agricultural pests, the government does not need to know who we are and what we are looking for in order to deliver the information we need.
If governments replace the anonymous delivery of information with e-government "customer-based" services, we will lose our ability to read (or even look for information) privately. (If you are not convinced that privacy is important, see Privacy: "I have nothing to hide".)
Filering out what we want. It seems almost counter-intuitive to say that personalization of web sites would make it harder to find what we need. Surely, personalization is designed to make it easier to find what we want, isn't it? Take the example mentioned in the NextGov article above: Imagine you live in an area that has just been damaged by a flood or a hurricane and you go to the FEMA home page. Wouldn't it be great to have the website "know" where you live and immediately show you links to specific services available and relevant to you? It would, but this example is not typical of all our interactions with government and therein lies a problem for relying only on customization.
Those who examine how people use the web have long understood and documented that customization of search results and browsing can do more to limit our understanding than enhance it. See, for example, Nicholas Negroponte or David Weinberger in 1995, and J.D. Lasica or Cass Sunstein in 2001.
And now Eli Pariser has written a book (The Filter Bubble: What the Internet Is Hiding from You) that documents how "the hidden rise of personalization on the Internet is controlling -- and limiting -- the information we consume." Pariser says that, when we are seeking information, "personalization" silently filters out relevant content as it tries to predict what we "want." (See Pariser's excellent TED talk for more details and examples: Lunchtime listen: Eli Pariser on filter bubbles.)
Do we want governments to favor "customers" who require "personalization" over citizens who are seeking information? I worry that such an approach will likely lead to government web sites that silently filter out relevant search results in an attempt to show you what the government (or Adobe) thinks you want. If we do not know how this process works and if we have no control over whether or not to use this functionality, we will end up not knowing if we have found what would be most relevant to our information needs. This would be bad. As we know, If It Is Too Inconvenient, I’m Not Going After It. Citizens seeking a broad array of information are not the same as customers wanting to buy a single product. Governments delivering a cornucopia of information are not the same as businesses trying to persuade customers to buy the shiniest, newest, highest-profit-generating product.
How do you preserve something that you can't get? As we move to the delivery of government information through dynamic web sites (whether "customer" driven or not), we face an increasing problem of preserving that information because we have no direct access to the information that needs to be preserved.
In order to preserve information (even digital information), we require an "instantiation" of that information -- a digital object to preserve. In the past, information was instantiated in physical books, pamphlets, maps, journals, posters, and even microfiche, CD-ROMs, and DVDs. Although some government information today is instantiated in PDFs and spreadsheets and even static web pages, government information is increasingly instantiated in databases that are not directly visible to users. When libraries (or GPO) cannot get copies of these databases, they cannot preserve them.
Websites use those databases to present selected information to users who visit web pages or who request information through searches. "Customer-driven" web sites will ensure that two people who make the same query or who visit the same URL will get different information. (To use the FEMA example again, if I live where there was just a flood and you live where there was just a hurricane and we both visit a customer-driven FEMA web site, I'll get flood information and you'll get hurricane information.) Web harvesting will be insufficient for preservation under these conditions.
The essential problem here is that, if agencies see their information mission as one of processing transactions with individuals rather than one of creating and delivering preservable instantiations of information, it will be difficult if not impossible for digital preservation to be complete or accurate or successful. Gertrude Stein might say of the lack of access to preservable digital objects, "There is no there there."
Concerns
At FGI, we are not technological determinists. We don't believe that the existence of software such as Adobe's CEM will inevitably lead to loss of privacy, harder to find information, and the inability of libraries to preserve digital government information. As noted above, there are circumstances where use of such software could yield better service and make it easier for users to find the information they need. We believe that thoughtful management of digital technologies can result in easier access and new functionalities without sacrificing long-term, free, public access to government information.
We also know, however, that technology is political and that sometimes organizations make bad technological decisions for apparently necessary reasons. Our concern is that agencies are under pressures that could easily lead to bad decisions and that software such as Adobe's CEM could make it easier to make bad decisions. Specifically, agencies are under pressure to reduce the number of government web sites and to streamline existing websites using new technology-based plans to improve their customer service at the same time that budgets are under increasing stress, open government initiatives are being reduced drastically, and GPO is being hit by big budget cuts.
Our concern is that these pressures will result in bad decisions. We worry that agencies will not add new, much-needed functionality to existing web sites, but will instead replace a citizen-centered model with a customer-center model. We worry that such a substitution will result in a loss of privacy, a loss in information-based functionality in favor of product-based functionality, and that all of this will make it even harder than it is already to preserve digital government information.
We agree with OMB Watch that information is a customer service and hope that agencies will keep this in mind when they make their information-technology decisions. But we worry that hard-pressed agencies will not.
Solutions
We believe that those (including GPO and FDLP libraries) who are interested in preserving government information should address the task of preserving the databases of government information that drive dynamic web sites. The information behind even customer-based transactions needs to be preserved; the transactions themselves do not. A model for this already exists with Census data. The Census Bureau has been able to provide a dynamic, database-driven web site and, at the same time, provide the databases behind the web site as preservable digital objects.
Preserving databases is a more complex task than preserving monographs or PDFs (see for example The Preservation of Databases, by Kevin Ashley, Vine, 34 (2004), 66-70), and agencies that personalize the delivery of information will have to ensure that personal information is kept separate from agency information, but database preservation and privacy protection can be accomplished. But to do so will take an active commitment.
Continue readingDisintermediation
Joseph J. Esposito, an independent management consultant to for-profit and not-for-profit clients, has written a nice post at the Scholarly Kitchen about disintermediation:
- Disintermediation and Its Discontents: Publishers, Libraries, and the Value Chain, by Joseph Esposito, Scholarly Kitchen (April 18, 2011).
Libraries are selective; they help guide readers to materials of higher quality. Libraries have purchasing power, which saves money for readers. Libraries provide a suite of tools for organizing publications and helping readers find what they are looking for. Libraries provide so much value that most people want them to be bigger.Disintermediation occurs when one link in the chain is bypassed. This can be caused by the link losing value, but it can happen for other reasons and can result in destroying the value provided by that link. How does this relate to the FDLP and government information? As we've noted here and here and elsewhere before, users of government information no longer need to go through FDLP libraries to get government information. And, as many others (including Ithaka S+R) have noted, FDLP libraries no longer have a monopoly on free government information, have no "purchasing power" advantage, and so do not save readers money. That particular value of libraries in the information value chain no longer exists and that results in government information users bypassing libraries for their government information needs. Some (including Ithaka S+R) have concluded from this that libraries can rely on online access to government information stored on government-controlled web servers and create a service-only model of libraries without collections. But this view overlooks the other important values that libraries add to the value chain. These include libraries' selection of materials of interest to particular user communities, their tools for organizing information to make it easier to discover, their tools for making information easier to use, and their commitments to freedom to read, user privacy, and long-term free public access to information. It also overlooks the ability that libraries have (but which government agencies for the most part do not have) to build collections that combine government information with non-government information. In short, it overlooks the importance of digital library collections. Joe makes another good point that is equally relevant to FDLP libraries: that, when we see a link in the value chain being bypassed, we should be asking what effect management decisions had in making that link lose its value.
[D]isintermediation lends itself to a version of technological determinism. Because the Internet makes it possible for an author to have a direct connection to a reader, therefore, it is assumed, authors inevitably will connect directly to readers. This ignores the role of human agency. ...[D]isintermediation, in other words, is an outcome; but the input is management strategy. Rather than talking about disintermediation, we really should be talking about the things that affect management decision-making and strategy and to take control of them.Thus, shouldn't we be asking, If users are bypassing libraries for their government information needs, what decisions are libraries making that make the library of less value to the user? In some cases users may not be aware of value lost. If governments fail to preserve all the information that users need, users will not be aware of this until they find information missing -- at which point it will be too late. In other cases, users may find that getting some information easily (e.g., using google to search the web and find some possibly-relevant government information) is better than using primitive hard-to-use library tools to find some possibly-more-relevant government information. Librarians may say that users "should" use libraries and they'd find "better" information if they did; but making that argument will not attract users. Providing better services will. If we look at what services users do use, we will see that they tend to be services built on top of digital collections. ProQuest, for example, does not build indexes that point to government web servers; it collects digital information and builds services on top of that. In short, libraries could create new value in the government information life-cycle by building robust services on top of rich digital collections (FDLP: Services and Collections ). Or, as Joe says,
[I] think of it as the creation of a new value chain, with the stress being given to the new value that is created.Continue reading
Access vs.Ownership
November 7, 2011 / Leave a comment
Those of us of a certain age remember the debates in libraries over "access vs. ownership." We don't see those terms used as much any more, but the issue remains with us as libraries increasingly opt for a service-only, libraries-without-collections model in which they license access to information rather than acquire information that they can carefully select, organize, preserve, and for which they provide not just access, but access and services customized to their user-communities.
The distinction between having "access" to information -- where the access (and fees) are controlled by others -- and owning information has mostly been too subtle for the popular press. You can see this as the popular press regularly refers to Google as a "Library" and now refers to Amazon's new e-book loaning feature as a "lending library." This loose use of the term "library" diminishes its association with free-access libraries that are run by and accountable to their communities and replaces it with an association with fee-based commercial services accountable only to stockholders or company owners.
So I found it very interesting to see not one but two recent articles in the consumer press that make a clear distinction between access and ownership and make at least a tentative argument in favor of ownership even for individual consumers.
Maybe if the consumer press continues this trend and continues to point to the distinction between access and ownership, the idea will migrate to libraries and we'll begin to see more libraries fighting to control information for their communities. That would be a welcome turn of events. We'd be able to get back to valuing services and collections.
Continue reading →Continue Reading →