On the Need for a General Purpose Digital Object Repository

Digital objects — we’ve all got ‘em. Billions and billions of them. And we put them in individual content silos, stratified along such unhelpful lines as media type, owning entity, and other equally meaningless categories. At least meaningless to the end user. So, let’s ask ourselves: what is the job the user is trying to get done? And how can we structure our digital object repositories to help them out?

What is a Digital Object?

Germany is at it, too

This just in — at least to my INBOX — Germany is working on a unified repository as well. Called the eSciDoc project, it closely mirrors what the DRC is going to be:

The aim of the Max-Planck Society’s sInfo program is to significantly improve the effectiveness of its
scientists and institutes by systematically exploiting the new technical opportunities (Internet,
digitalization, communication, open access). It addresses many facets of scientific work: information
retrieval, processing and evaluating information, distributing and storing information, scientific work in
the laboratory and at the desk, scientific work performed by individuals and in groups.

Repositories Visualized

On 12/14/05 10:26 AM, Richard Green wrote on the sakai-library mailing list:
The RepoMman projectat the University of Hull, UK, is looking into the area
of workflow as related to an institutional repository. Hull sees a digital
repository as being a tool for its users, assisting them to develop a ‘piece
of work’ (a generic term intended to cover almost anything) from inception
to final form – supporting such things as development, collaboration and
versioning along the way. In other words, we see a repository as much more
than a container only for ‘finished’ digital objects. We are playing with
the acronym ‘AMP’ (access, management, preservation) to describe some of the
related functionality.