40 likes | 119 Vues
Managing Your Institutional Web Gateway: The Future. Phil Cross ILRT University of Bristol Bristol phil.cross@bristol.ac.uk. Brian Kelly UK Web Focus UKOLN University of Bath B.Kelly@ukoln.ac.uk.
E N D
Managing Your Institutional Web Gateway:The Future Phil Cross ILRT University of Bristol Bristol phil.cross@bristol.ac.uk Brian Kelly UK Web Focus UKOLN University of Bath B.Kelly@ukoln.ac.uk UKOLN is funded by the Library and Information Commission, the Joint Information Systems Committee (JISC) of the Higher Education Funding Councils, as well as by project funding from the JISC and the European Union. UKOLN also receives support from the University of Bath where it is based.
Things To Think About • Some issues to consider: • Simple HTML pages vs. back-end database • Which back-end database? • Back-end database philosophy (shrink-wrapped vs. open source; licensed vs. free) • Who maintain it (Library, Computing Service, web editor?) • Should institutions run portals at all? • If they do, how do users find it? Should it be on the Intranet?
Other Issues • Unfortunately there is no time to address these other important issues Q Should you catalogue resources on your portal, or leave that to national gateways Issue: National gateways are funded to do this work Q Should a portal be on the Intranet? Issue: Visitors to your public web site may find your portal and then leave Q Should your portal link to non-web resources? Issue: eLib Hybrid Library projects are helping users find solutions, not resources on web sites? Q How many portals – one or many? Issue: Should we expect every dept to produce a portal? Q What are the important technologies for providing a portal? Issue: How do XML and RDF fit in? Q Should you link to software from your portal? Issue: Link to Netscape or UK Mirror?