Editorial summary · SDL 2006

Who pays after the grant ends

The original paper at this address did not survive. In its place, the editors summarize a theme that ran through the 2006 symposium: business models for digital libraries.

EventSustaining Digital Libraries, 2006
Page typeEditorial summary
ThemeBusiness models and sustainability
Original paperNot preserved
PDFMetaScholar briefing: Sustaining Digital Libraries/publications/StrategiesforSustainingDigitalLibraries.pdf
MetaScholar — Editorial summary · SDL 2006
record.xmlnotes.mdsources.txt
All collectionsSymposia06Projects07Photographs02Documents06Journal20
Editorial summary · SDL 2006
oai_dcindexedneeds review
1<record status="active">
2 <dc:relation>/events/2006/sdl/viewpaper.php?id=6</dc:relation>
3</record>
Record
EventSustaining Digital Libraries
Page typeEditorial summary
ThemeBusiness models and sustaina
Original paperNot preserved
Publish

About this page

This address once displayed a paper from the Sustaining Digital Libraries symposium, held by the MetaScholar Initiative at Emory University's Woodruff Library on October 6, 2006. The paper, its author details and its abstract were not preserved in the material the editors could recover.

Rather than leave the page empty or guess at its contents, the MetaScholar editors have written an editorial summary of one theme that ran through the whole symposium: how digital libraries can pay for themselves over time. This is our synthesis, not the original paper. It names no presenter, because we cannot confirm who wrote what.

The theme is a fair representative. The symposium was organized around exactly this concern. Its program set funders, national programmes and organizations from outside the library world side by side to compare how each kept services running.

For the published record, see the editors' briefing Strategies for Sustaining Digital Libraries.

Editorial summary · SDL 2006
Who pays after the grant ends

The core problem

Most digital library projects of the period followed the same arc. A grant paid for building: digitization, metadata, software and a public site. The project launched. The grant ended. Then the costs that never stop arrived.

Those ongoing costs are easy to list and hard to fund:

  • Storage and backup that grow every year.
  • Software updates, security fixes and migration to new platforms.
  • Staff time for metadata corrections, user support and new content.
  • Format migration, as file types age out of common use.

Grant programmes usually funded innovation, not maintenance. That left institutions to absorb running costs into existing budgets, often without planning for them. The predictable result was services that froze, then decayed, then disappeared.

The 2006 symposium treated this as a structural issue. The question was not how to find one more grant. It was what kind of organization can carry a service indefinitely.

Models on the table

Across the symposium's panels, several broad approaches to long-term funding were in view. The editors describe them here in general terms.

ModelHow it paysMain risk
Institutional base budgetHost library absorbs costsCut when priorities change
Membership consortiumMembers pay annual duesMembers leave if value is unclear
Public programmeNational agency funds shared infrastructurePolitical and budget cycles
Earned revenueServices or content sold to usersConflicts with open access

The presence of ICPSR and Amazon.com on the program pointed at the last two rows. ICPSR showed that a membership model could sustain research data access for decades. Amazon showed what a service looks like when operating costs are planned from the first day.

No single model fit every library, and most real services mixed two or three. The useful outcome was the habit of naming the model explicitly, so that its risk could be planned for instead of discovered.

quality metrics · sample collection
findability
82%
completeness
67%
consistency
74%
rights clarity
58%
link health
91%

What happened next

In the years after 2006, the membership model became common for shared preservation. The MetaScholar Initiative's own MetaArchive network moved toward a cooperative structure, discussed at the 2007 distributed preservation workshop. Other consortia followed similar paths.

Funders also changed. Many began to ask for data management and sustainability plans in proposals. That did not solve the problem, but it moved planning to the start of projects, where the symposium had argued it belonged.

Technology helped at the margins. Cheaper storage lowered one line of the budget, while hosted platforms moved some maintenance to shared providers. Neither removed the need for people who understand the collections.

The hardest lesson was about scope. Services that tried to do everything for everyone were hardest to sustain. Services with a clear community and a narrow purpose lasted longer. That pattern is visible across the MetaScholar projects themselves.

The editors return to this subject in Sustaining digital libraries: funding models, which compares the models above with current practice.

preservation nodeverified copyreplication path