2. Document server and deposit system

A deposit system for ETDs or for digital resources in general has to concentrate on very specific tasks, building a small and somewhat exotic subset of what we are used to call "digital library" functionality. New self-publishing concepts have taken over archiving terminology and challenge its contents. Arnoud de Kemp from Springer publishing house (Heidelberg, New York, Berlin) said once "Publishing an e-journal is more than just putting it onto a web server". Using his example, I would derive the statement "Archiving is more than just implementing a web server and storing ETDs on it". A deposit system is built for the future, and it is sometimes hard to show its benefits and efficiency in the present. Therefore, we follow the concept of strict functional separation: library management system, document server and deposit system should be interoperably based on open interfaces and protocols, and it should always be possible to cope with strengths and weaknesses of each building block separately. Core business of deposit libraries and mass usage oriented libraries is different: they complement each other concerning high performant access and prodeures for guaranteeing long term avaliability. This also affects responisibilities for ETD life cycle management.

© This publication and its compilation in form and content is copyrighted. Every realization which is not explicitly allowed by copyright law requires a written agreement. Especially, this holds for reprography and processing / storing by electronic systems.