Reference Manual

More documents

Recommendations

Info

Software Required 1The current version of Xtrieve (4.10a) is significantly improved over previous versions, the MUSE staff can only support questions about that (or later) version. 1-1 1 Introduction MUSE is a database-management system for natural history collections which operates on PC- or MS-DOS microcomputers. It is designed to increase the efficiency of many tasks associated with collections management. Data entry and editing, reidentification of specimens, management of loans, printing of specimen labels and loan invoices, and querying of the data files are all supported. MUSE software, documentation and support is made available through a National Science Foundation grant, awarded to Julian Humphries of Cornell University. Initial versions of the program were designed exclusively for ichthyological collections. However, current versions of the program support a variety of disciplines, including herpetology, ornithology, mammalogy and other natural history collections. Btrieve (from Novell, Inc.) is the "database" engine behind MUSE; it is a memory-resident program that translates requests for data into actual reads and writes to the database file system. You do not need to buy Btrieve because we are allowed to redistribute the portion of it which you need to run MUSE and Xtrieve (see below); Btrieve is included in the MUSE software package. If you have a Novell network, Btrieve is also packaged with Netware and can be installed on the server. You will need some kind of text editor to alter certain files used by MUSE. Either the text mode of your word processor or a pure ASCII editor will suffice. Xtrieve (also from Novell, Inc.) is the companion product to Btrieve. It is used to query the data in MUSE data files and print reports. If you choose to use Xtrieve (currently packaged as "Xtrieve Plus" which includes a report writer, and both single-user and network versions in the same package) you will need to 1 purchase it yourself. Xtrieve Plus can be bought for under $600 . We buy most of our software from a company called Programmers Connection in Hartsville, Ohio (phone number, 800-336-1166), but Software City and Egghead Software are also inexpensive sources. The MUSE newsletter contains information on other front ends which can query MUSE data files. Please be aware that using Xtrieve with MUSE generally should be limited to performing queries and producing reports. Because adding or editing data in Xtrieve increases the probability of data corruption)by bypassing MUSE's datachecking features)Xtrieve should be used only as a last resort for any modification of MUSE data. Try always to enter and edit data within MUSE (or with special MUSE utilities, such as Tdutil for modifying the taxonomic dictionary). 1 Introduction
Hardware Required Installing MUSE MUSE runs on microcomputers with Intel 8088 through Pentium industrystandard microprocessors with either color or monochrome video systems. Each computer should have at least 640 kilobytes of memory although MUSE only needs about 524k. Collections of larger size and with more users will find distinct advantages in the newer machines with faster processors (80486 and up). Likewise, larger collections will require more hard disk storage capacity (one or two 500-1000 megabyte hard disks). Also, a local area network (e.g. Novell Netware), with a fast fileserver and large hard disk, is strongly recommended for many medium and all large collections. For those computers with additional memory beyond 640k, either extended or expanded (see your computer manual for explanations of these memory types), MUSE can take advantage of such memory in two ways. The memory resident program, Btrieve, will load part of itself into expanded memory by default. Memory usage will be cut from approximately 80k to 40k. MUSE itself utilizes an overlaid structure for the executable file. This means that code is not actually loaded into memory until it is needed. If you have either expanded or extended memory available, MUSE will store overlays there, as opposed to on disk. Either way will work, but response will be quicker with memory cached overlays. Through the use of SLATE, a printer database software utility, MUSE supports over 800 models of dot matrix and laser printer. Users can design specimen label and loan invoice forms for any supported printer. Contact the MUSE Project for current information about printer support. We highly recommend that you get a laser printer for invoices, reports and certain labels. IMPORTANT: If at your site, data for two or more separately-cataloged collections are to be stored in separate subdirectories but accessed from a single MUSE subdirectory, your installation procedures will be different. Refer to the alternate instructions received with your MUSE package. To install MUSE on your hard disk, you should follow these steps: NOTE: Depending on floppy disk density, you may have received MUSE in a set of one, two or three disks, the sets differing slightly in the names and arrangement of the files they contain. In the instructions below, alternative choices are enclosed in square brackets "[ ]". In each case, choose the alternative appropriate for the file names on your disk(s). 1) Make back-up copies Make back-up copies of the MUSE floppy disk(s). Store the original disk(s) and use the copies to install MUSE. 2) Create subdirectories at the root directory On your hard disk, create three subdirectories at the root directory level (e.g. C:\) to contain the MUSE files. Using the mkdir command create the three subdirectories: a) Name the first subdirectory MUSE; this subdirectory will store most of the MUSE files. 1-2 1 Introduction
Page 1 and 2: Tutorial and Reference Manual Julia
Page 3 and 4: The MUSE Project Building 3, Resear
Page 5 and 6: iii About This User's Guide This ma
Page 7 and 8: List of Figures Figure 1 Partial da
Page 9: 7 Adding New Records to the Databas
Page 13 and 14: 5) Check CONFIG.SYS file 1-4 a) Typ
Page 15 and 16: Hierarchical Taxonomic Dictionary T
Page 17 and 18: 1The two groupings are "entities" i
Page 19 and 20: using that combination. For example
Page 21 and 22: NOTE: If, at your site, data for tw
Page 23 and 24: Answering Prompts Configuration Exi
Page 25 and 26: Locality 1) To view Locality or Sit
Page 27 and 28: Move below the bottom margin of the
Page 29 and 30: IF THEN Generic and specific MUSE a
Page 31 and 32: Return to Primary Next Primary Reco
Page 33 and 34: In certain cases, a field may be se
Page 35 and 36: Proofing Locality Records Figure 3
Page 37 and 38: Figure 4 Deaccession Screen The dea
Page 39 and 40: . Figure 6 Print List Form a line i
Page 41 and 42: first retrieve the list with that n
Page 43 and 44: Editing a Loan form which appears,
Page 45 and 46: 2) For complete or partial returns,
Page 47 and 48: select "Fix Mistake" from the "Loan
Page 49 and 50: Name line TL|Tiny Labels/Laser * de
Page 51 and 52: Forms per Page in the "Attribute" c
Page 53 and 54: Optional Parameters form_x_gap# - S
Page 55 and 56: ox - Print graphic block or line Sy
Page 57 and 58: to be printed on the line or form;
Page 59 and 60: RREPORT.EXE (Part of Fixddf) HTDXPO
Page 61 and 62:
-: To view other files while adding
Page 63 and 64:
APPENDIX D: Sample FORMCAP File Sam
Page 65 and 66:
small_step#3.5 (left_margin, 6.4) "
Page 67 and 68:
(left_margin + 16.0, *) "Count" (le
Page 69 and 70:
Figure 1 Jar Label/Dot Matrix Figur
Page 71 and 72:
Figure 5 Multi-lot label for tank,
Page 73 and 74:
APPENDIX E: Configuration Items Sys
Page 75 and 76:
APPENDIX F: Creating Site Names In
Page 77 and 78:
of data is identical for all such s
Page 79 and 80:
Help ii, iii, iv, 1-3, 3-1, 5-1, 5
show all

Reference Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?