Repository is one of those words which needs to be accompanied by a qualification: just what do you mean in this context by repository?

We are moving away from thinking about a repository as a 'bucket' into which we pour content. And towards a sense of repository as a set of services on managed objects. Different repository frameworks might provide different services in different configurations.

This is on my mind as I have just been looking at a presentation [pdf] given by Herbert Van de Sompel at Olybris 2005 in Kos.

Herbert sketches an environment in which libraries manage institutional intellectual assets in 'repositories'. Crucially, they will also facilitate the emergence of 'value chains' across repositories by building services which consume, aggregate, analyse, mine, link, recommend, .....

This service recombinance depends on agreed interfaces, which allow information objects to flow between repositories and between repositories and consuming applications. It is an example of how services will increasingly be oriented towards 'intermediate consumers', where systems, rather than humans, are significant users.

If you want your thinking stretched over the weekend, check out Herbert's presentation ....

Comments: 1

Apr 23, 2005
Dorothea Salo

Thanks! This is a useful pointer.

I do wish we'd start looking a bit harder at the other end of the chain, though -- editing, peer-review, and production. I stubbornly maintain that if we're serious about making headway into the scholarly-output domain, we have to take on these services as well.