Maintenance of data A data object should be created once Dont overlap work on maintenance Optimise maintenance User data should be maintained locally (LDAP) Bibliographical data created centrally Administrative data should be maintained locally On-line subscription data maintained centrally
Subject gateways Service tailored to user community but Do we all need to select and classify resources? Alternative methodologies - technical (e.g. OAi) - organisational (how do we split the work - if we need to do it)
Local-national-international Index Subject, region,…. Quality
Library A Catalogue Own development DEF Journals Links Digital resources Navigation DEF Catalogue
Library A Library B Library C Navigation data Common data Link Etc. Catalogue Links On-line Journal data Search Engine Own Developed software DEF developed/purchased software Local data
SB development - Web User- and library involvement –Focus on different needs of different target groups –Shared components - if possible Technical platform –J2EE –Open Source (JBOSS and TOMCAT) –Portlets (Jetspeed)
Common Services Links - subjectgateways (Electronic) journals Education Search engines Webvise- and similar DEF-key (LDAP) etc.
Summary Optimise relative to object and its description (-> central) Optimise maintenance of data (-> local) Customise relative to target group, user involvement Delivery time is a parameter Money flow has to be taken into account Quality has to be guaranteed