Hi David, I imagine you've already considered these thoughts, but just in case, I have to add the following:
What ever route you take, developing proprietary databases on your own, bringing in expert consultants, or going with something off-the-shelf, I can't stress enough the importance of taking a team approach. As stated by others and as you probably already know, databases these days are not usually a stand alone operation. Therefore the most successful projects involve input from a variety of specialists - - people with subject expertise, people with database expertise, people with knowledge of network and web technology, and perhaps most importantly, active and continuous participation from the people who will be using the database for various purposes. If you haven't already done so, I would think long and hard about what you want to be able to do with this database, not only now but down the road. Then I would try to get input from as many of the users and people with other specialist knowledge as possible, and put this on paper. I guarantee that your requirements will change as you go along. It's helpful to have a written document a reminder of how far your current goals and objectives have evolved since the beginning (and whether or not this is appropriate). It will also be helpful to the next person who comes along. I believe that building various types of models and a repository of information about the database is also essential (and you would be surprised to know how many projects fail to do this). Modeling forces you to think things through and truly understand the way the database will need to be used. It can also help you communicate ideas, particularly if you need help from programmers. You're right to want to brush up on basic database and data modeling skills. Even if you ended up working with a consultant, the more you know, the more likely it is you will end up with a database that meet your needs. The classic work on relational databases is C.J. Date's, Introduction to Database Systems (it's pretty expensive, but I bet you can find it at the local library). Be forewarned however, that this isn't for the faint of heart. Several editions have been published over the past 25 years. The most recent one includes object-oriented approaches (although Date isn't necessarily unbiased in his discussion of the pros and cons). You may need to skip around a bit and will probably only find two or three chapters that meet your current needs. You might also want to take a look at journal named Intelligent Enterprise (formerly Database Magazine and also on the web I think) for tips and suggestions and just to tap into what's going on in the database world. Another possiblity is to subscribe to Techies.com and take one of their online classes on relational databases. These courses are pretty simplistic though. As far as data modeling goes, a good start is a little book by G. Lawrence Sanders, surprisingly entitled Data Modeling. As you've probably noted, there are lots of different types of notation out there and it can get confusing. Which ever notation you use, you might also want to take a look at UML (Unified Modeling Language) since it has been proposed as a standard. And speaking of "standards," as mentioned already in one message, there are several of these already out there for museum data. If you haven't seen these already, you might want to take a look at what some of the ICOM committees have been doing over the past few years at: http://www.cidoc.icom.org/ As already mentioned, the MDA is another good source. These standards are a good place to pick up ideas, although chances are you'd have to modify them to meet your specific needs. Nevertheless, they're a helpful place to start. Wishing you the best of luck with your project, Jackie Zak [email protected] >>> [email protected] 01/24/01 11:43AM >>> David- Have you received any replies off list about this? I am very interested in furthering my education in database technology. Tracie Umbreit Research Associate Kittleman & Associates -----Original Message----- From: Farrell, David [mailto:[email protected]] Sent: Wednesday, January 24, 2001 10:29 AM To: 'MCN Listserve' Subject: Courses and Reference Works on Database Design Hi Everyone, I am currently converting our collections management database from DOS based proprietary software to MS Access and I would like to know if there is anyone who has been down the same road with any recommendations of works on relational systems design and data modeling. I am aware of the risks and disadvantages of doing it ourselves with generic database software rather than using proprietary software, but it was felt that it was worth having the control and flexibility that this option would provide. I have had a good deal of previous experience with Access but I feel that I need more knowledge of relational systems design. I would like to know if there are museum professionals who are not programmers who took courses on this subject, and if so was it helpful? Also, are there any reference books on the subject which anyone would recommend? Searching on the internet I found a few books on database design but I am not sure which ones would be appropriate for some one with no programming experience. I looked for these books in a couple of large book stores in Toronto and only found reference books specific to particular software. Does anyone have any recommendations? Thanks in advance, David Farrell, Collections Assistant Peel Heritage Complex 9 Wellington Street East Brampton, ON L6W 1Y1 (905) 791-4055 ext. 2108 (905) 451-4931 fax www.region.peel.on.ca/heritage/index.htm ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.Region.Peel.On.Ca **********************************************************************
