Message-Id: <mailto:199410050329.WAA29425@library.wustl.edu> Date: Tue, 4 Oct 1994 22:21:44 -0500 From: "Stephen J. Fletcher" <mailto:sjfletch@INDYNET.INDY.NET> Subject: Re: Mac Quadra To: Multiple recipients of list IMAGELIB <mailto:IMAGELIB@ARIZVM1.BITNET>
On Tue, 4 Oct 1994, Yturralde wrote:> We have recently purchased a couple of Quadras for the purpose of
> processing part of our photograph collection. Does anyone use these? Can
> you advise on software for the database element of the project? Are all
> scanners compatible?
>
> Rudimentary questions, probably...my experience is in the IBM realm,
> though, and I guess now I should get Mac-literate.
>
> Thanks for any information.
>
> Victoria Yturralde
> mailto:vmyturralde@ucdavis.edu
>
It is hard to answer these questions without soundy preachy. Please know that is not my intention. It's just that buying a computer without knowing what how it will be used is a mistake that I have heard about often. I hope what follows can help those who are asking themselves the same questions.
"What computer to buy" is the *last* of three basic questions a person must answer. All too often people buy a computer, then buy a software product, and then try to figure out what to do with the software. *This method of automating is the exact opposite of what should be done.*
Broadly speaking, there are three main steps to automation:
the first thing that a person deciding to automate *must* do is to identify what data is to be organized, what charactersitics that data has (for example, numbers to perform mathamatical functions, dates, length of the data, etc), how the data will be organized, and how the data will be used;
the second step is identifying what software will accomplish the tasks you wish to perform on the data, and what operating system supports that software;
and *lastly*, what hardware system the software requires.
The detailed process that one undertakes to determine the answers to these questions is called systems analysis. There should be several texts out there that explain the process. The text I used while in graduate school ten years ago, _Principles of Information Systems for Management_ by Ahituv Neumann is the only text with which I am familiar. It may be updated by now; others out there may know of better books.
Why is this approach important? What happens if the "perfect" system for you runs on software that cannot run on a Machintosh? What if you buy a software pack that has limitations that keep you from using the data to provide you with the information you need? How do you determine what data needs to be automated, and what data does not need to be --or can't be-- automated?
You may still use the systems approach to answer the first two questions in hopes of identifying a software package designed for the Macintosh that meets your needs.
I hope this helps others who are considering the same questions.
Best regards,
Stephen J. Fletcher Curator of Visual Collections Indiana Historical Society 315 W. Ohio Street Indianapolis IN 46202 317 232 1879
mailto:sjfletch@indynet.indy.net