Home » Library (Page 22)

Category Archives: Library

Our mission

Free Government Information (FGI) is a place for initiating dialogue and building consensus among the various players (libraries, government agencies, non-profit organizations, researchers, journalists, etc.) who have a stake in the preservation of and perpetual free access to government information. FGI promotes free government information through collaboration, education, advocacy and research.

Questions and answers about the future of FDLP

Roger C. Schonfeld, the Ithaka S+R Manager of Research, asked us several questions in a comment to a post here last week (Who Do You Serve and What Do You Do?: Defining Your Role to Defining Your Role to Ensure the Future of Our FDLP). These were good questions and we welcome the opportunity to spell out some specific ideas we have here at FGI about the future of the digital FDLP. Roger, Thanks for your comments and your questions. (And thanks for noticing that broken link! I fixed it.) Here are few quick responses to your questions. (I'll answer the question about libraries holding overlapping or even identical digital collections separately.) Q. Is your proposal that, as a condition of participation, every Federal Depository Library be required to hold locally at least some kind of sub-set of the digital/digitized collection? A. No: No more than we require every depository to have fiche. I do think, though, that it is not too idealistic to imagine a future when every FDLP library (or most of them, or hopefully at least hundreds of them) will have digital collections that include FDLP content. I think that digital deposit could become a standard part of depository status in a number of different ways, probably starting out slowly and building up over time. I think that the strength of the FDLP has been and will be its flexibility and a digital FDLP should have new kinds of digital flexibility. The design of exactly how to achieve that should be a process, not an either/or choice today. I would like to see us use a process different from the one we used to get microfiche into the FDLP because that process took years to implement. I would prefer to see a phasing in of digital deposit that would allow FDLP as a whole to move faster even as individual libraries moved at their own speed. I am not a lawyer, but I think that a simple change to SOD 301 to allow for digital materials to be deposited and for depositories to select digital format would be an easy first step. I would think that phasing in digital deposit would allow for the community as a whole to develop an infrastructure and skills and experience and a variety of models to accomodate different kinds of libraries and collections. Over time, I would guess, more libraries would develop the technical capacity to participate and would be eager to do so. Q. Or, do you see a complementary role for “virtual depository libraries” (see for example http://govdocs.library.arizona.edu/policy.html) and similar models that would rely on GPO and/or other libraries as collections providers? A. I would like to see a digital depository program that would be flexible enough to include all kinds and sizes of libraries. That will be its strength. I think the key to digital deposit is that a depository library would have physical control (in the OAIS sense) of the material. I would think that a digital depository system would be flexible enough to allow partnerships between libraries as well, so that "physical control" might include partnerships among libraries. That might mean, for example, that two library partners (libraries "A" and "B") might share physical control though a shared data center or a data center at one of the partners. The "control" would consist of their shared administrative decisions over what was in the data center, how that material is organized and described and preserved, and the methods of access to that material. I can imagine a single library participating in several different partnerships as well. For example, a library might be part of a national digital law library and a regional water-shed library, both of which might include FDLP materials. I do not think that any library can currently claim physical control over anything in FDsys or at any federal agency. I do think that there is a place for libraries maintaining links to digital materials not in their physical control and that this can enrich their services. But, since a) anyone can do that without being a depository library and b) the library has no control over the materials they point to, I don't think that providing such a service by itself is an accurate or useful way to characterize or define what it means to be an FDLP library. It might be possible to design a digital FDLP in which maintaining links to materials in FDsys (for example) would be one of many characteristics or even requirements of a being an FDLP library. I can also imagine, using the example above, that an FDLP library "C" might point to materials in the possession of libraries A and B as well as having its own digital collection. I can imagine a couple of things that GPO could do to make the just-pointing-to-FDsys "virtual depository" model a more reliable, more technologically sophisticated part of a fully functional twenty-first century FDLP: 1) GPO could make FDsys an "interoperable" archive (in the OAIS sense) that worked with FDLP digital repositories. 2) Once there are at least a few large FDLP repositories, the FDLP library community could become part of the GPO "succession plan" (in the TRAC sense of the term) so that materials that GPO could no longer keep or preserve or provide access for could be easily migrated to FDLP libraries for preservation and access. Individual FDLP libraries could also rely on GPO and, as we get more digital FDLP libraries, other FDLP libraries for their own succession plans. This would at least solve a bit of the problem of pointing to things not in one's control: you could be at least somewhat assured that they were in the possession of the FDLP library system and not at the mercy of a GPO budget cut or mandated mission change. Finally, in an FDLP with digital deposit, we could have something similar to what is possible with DOIs that would allow maintenance of pointers to more than one copy of any particular item at more than one repository. (http://freegovinfo.info/node/2947) Q. Now that GPO is making more of the digital content available for bulk download, I’m curious what success looks like from your perspective A. Bulk download is a great thing to have, but it is merely a useful method of delivery, not a system of or replacement for digital deposit. Almost certainly it would be a useful tool for a digital depository system, but it is not synonymous with or, necessarily, a precursor of digital deposit. The strength and importance and sustainability of a digital FDLP will be found in those things that FDLP libraries can do or guarantee that they will do that are not done or cannot be done by others. I would think that digital deposit would include more than the ability to download in bulk. For example, a digital deposit might involve the commitment by the FDLP library to maintain FDLP-specific metadata generated at the time of deposit. That might include identification of the materials deposited as officially depository items, when they were deposited, version information, original source url, fixity information, provenance, and so forth. It might involved participation in a shared DOI-pointer system as noted above. It might include shared, reliable union catalogs and inventories and full-text indexes that could be built and maintained across depositories because of the commitments made by the participants. Success of a digital FDLP would have to include: - Digital deposit of digital materials into the physical control of participating FDLP libraries. - Agreements between GPO and FDLP libraries, and, probably, among FDLP libraries, for preservation and access. - Accountability of FDLP libraries for preservation and access. - When fully implemented, a digital FDLP would, in the aggregate (across all participating libraries), guarantee that every Title-44 digital object would be in the physical control of the FDLP community in addition to or instead of the control of GPO. Success could also be measure by other benefits that would, I think, also accrue (to GPO, to the public, to participating libraries) once such a system was in place. For example, it would be easier to develop and enforce new publication and metadata standards that would make preservation and long-term usability easier. It would be easier to create publication processes to identify and distribute instantiations of content (an obvious example: Census summary files) rather than trying to scrape dynamic web sites (which is almost always incomplete and unsatisfactory). It would be easier for the public to find and rely on government information they needed. It would be easier for libraries to build and maintain complete collections of information for their designated communities. It would be easier to keep track of and preserve "fugitive" government information and non-Title-44 information. I don't want to minimize the tasks at hand to do what I am proposing. But I also urge you not to be overwhelmed by libraries and librarians and, particularly, library managers who think this is an impossible or never ending task. This isn't a unique situation. I saw a similar situation in when the "impossible/never-ending" problems were overcome and libraries embraced what they once did not: A couple of decades ago, there were very few numeric data collections in libraries, but today almost every ICPSR member is a library and there are many data libraries in libraries. The software for building digital libraries and trustworthy repositories exists and is being improved all the time. To mention just one specific example, the LOCKSS-USDOCS project is already working toward the model of a successful digital FDLP library that I describe here. Other events outside of libraries and overlapping with libraries (e.g. the open data movement, citizen mashup and tagging, new forms of scholarly publishing and open access publishing, institutional repositories, print on demand, mandated deposit of publicly funded data collections, the so-called data deluge, etc.) are beginning to affect libraries and their roles. Libraries already are embracing and building digital collections. While digital deposit might have seemed far-out and impossible in 1993, it is now within our reach. At FGI, we see digital government information as the canary in the library coal mine. If government information librarians work on and solve the digital ingest/preservation/access issues for government information, their libraries will be able to generalize those solutions to other digital library collections. That would be a HUGE benefit to libraries in general and a big incentive for libraries to continuing to participate in the FDLP. Everyone wins. Continue reading

Continue Reading →

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:

  • Libraries as "service centers." You might call this the "libraries without collections" or the "librarians without libraries" model. This is the model designed by GPO in 1993. It is the model that ITHAKA, the parent organization of Ithaka S+R, has used as its own business model for Portico and JSTOR. This model is favored by the Association of Research Libraries, by many library administrators who apparently believe that it would be better if someone else took the responsibility of preserving government information and ensuring its long-term accessibility and usability, and by many depository librarians who do not have the support of their institutions to build and manage digital collections.
  • Libraries as "business centers." This model is an extension or complement to the above model because it, too, envisions libraries without collections. It sees the library as the agent that manages leases and licensing agreements with publishers and other producers (including government agencies). This model is advocated by ITHAKA, by commercial data providers who make a profit by limiting access to information to those who pay for it, by government agencies that have accepted that they must be self-supporting and thus sell their information, and by the information industry, which would like the role of libraries to be enforcers of rights-management. In addition, most libraries have already accepted this model for many classes of digital information by leasing access to databases or electronic journals instead of demanding their own digital copies.
  • Libraries that provide both collections and services. This is the traditional library model in the paper world and it is increasingly the new model in the digital world. Examples of libraries doing this include libraries and projects of all shapes and sizes: The California Digital Library, the Hathi Trust, the Scholars Portal of the Ontario Council of University Libraries, the Legal Information Archive of the Chesapeake Project, the North Carolina Digital Repository, the Stanford University Freedom of Information and CRS and FRUS collections at Archive-It, the University of North Texas digital government collections, the LOCKSS-USDOCS Network, the Historical Publications of the United States Commission on Civil Rights at the Thurgood Marshall Law Library at the University of Maryland, the many U.S. Government Publication Digitization Projects, and many more. This is also the model that private sector government information service providers use when they obtain copies of digital information so that they can provide services for that information rather than trying to provide services for collections that they do not hold. This model also fits the OAIS preservation model which requires that an archive "obtain sufficient control" of information in order ensure long-term preservation.

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 →

LOCKSS-USDOCS at Best Practices Exchange

I just got back from Best Practices Exchange 2010 (check out the growing list of available presentations and the twitter back channel!). It was a really solid conference -- a healthy mix of archivists, documents and other librarians, and technologists having project-oriented presentations with a healthy dose of discussion. The cherry on top was the engaging keynote by the David Ferriero, the Archivist of the US (AOTUS) (here's a good summary of AOTUS' talk). I was on a panel with Arlene Weible from OR State Library (Arlene gave a great talk on RAT, OSL's tool for collecting state documents -- I hope she posts her slides soon!) and presented about LOCKSS-USDOCS, the distributed documents preservation project. Take a look at the slides. We're looking for other participant libraries so email me if your library is interested (jrjacobs AT stanford DOT edu).

Continue reading

Continue Reading →

Letter to Deputy CTO Noveck: “Open Government Publications”

[UPDATE 9/23/11: It's come to our attention that scribd, the site that hosts the document below, does not make it easy for users to download. In some instances it appears as if the user has to subscribe to scribd before they can download. So I've attached a copy of the document below for your free downloading pleasure. JRJ] In early April, Michael Keller, Stanford University Librarian and my boss, had a phone conversation with [w:Beth Simone Noveck], US deputy Chief Technology Officer for Open Government leading President Obama's Open Government Initiative. Noveck requested a short report outlining how the digital FDLP would work. Below is that report outlining a distributed ecosystem, or publications.gov, that "would incorporate collaborative cataloging/metadata creation, as well as shared or Peer-to-Peer (P2P) technical infrastructure in which data and technological redundancy and collective and proactive action reign." As many of you already know, some of the pieces for a digital FDLP ecosystem are already in place. However, as our recent post, "The State of FDsys and the Future of the FDLP", showed, some of those critical pieces are on shaky ground to say the least. The report was forwarded to Bob Tapella and Mike Wash at GPO as well as Aneesh Chopra, Chief Technology Officer (CTO), Vivek Kundra, Chief Information Officer (CIO), and US Archivist David Ferriero. FDLP issues are now front and center to the movers and shakers in the Obama administration. But we'll need more libraries and librarians willing to step up and pitch in to make the digital FDLP ecosystem a reality.

Digital FDLP Ecosystem
Continue reading

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:

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 reading

Continue Reading →

Latest Posts

Latest Comments

Blogroll

Archives

Meta

Archives

Powered by WordPress / Academica WordPress Theme by WPZOOM