<HEAD> <TITLE>"Systems for Museums"</Title> </HEAD> <BODY> <A NAME="pgtop"></A> <A HREF="STIPPLE_Presentation_1htm2.htm"><Img Src="flrarrow.gif"></A> <A HREF="#pgbot"><Img Src="flnote.gif"></A> <A HREF="mailto:rob.dixon@erros.co.uk"><Img Src="flmlsend.gif"></A> <BR> <IMG BORDER=0 SRC="STIPPLE_Presentation_1htm.gif" > <HR> <A NAME="pgbot"></A> <UL><LI>But often relatively few examples of each type <LI>A larger museum may have several (or many) million objects that are uniquely identified whilst a company may have large quantities of, say, nuts and bolts but these are not individually numbered <LI>Paintings have painters, prints have engravers, artists and print publishers, etc.. No generic term of "maker" is adequate <LI>Yet building a solution for each object type is far too expensive using traditional methods of system development <LI>Systems for registrars, curators and conservators need to store different information about the same objects. <LI>Web sites need to present part of the same data in a different way <LI>This is not a good idea. <LI>The records for books in a library should also be used for bibliography for people and objects </UL> <HR> <A HREF="#pgtop"><Img Src="flpage.gif"></A> <ADDRESS>Rob Dixon <A HREF="mailto:rob.dixon@erros.co.uk">rob.dixon@erros.co.uk</A></ADDRESS> <FONT SIZE="-2">Published by Lotus® Freelance Graphics® </BODY>