Proceedings-Symposium on Cheatgrass Invasion, Shrub Die-Off

Proceedings-Symposium on Cheatgrass Invasion, Shrub Die-Off

THE FIRE EFFECTS INFORMATION SYSTEM: A TOOL FOR SHRUB INFORMATION MANAGEMENT Anne F. Bradley ABSTRACT Effects Information System or FEIS. FEIS is a computer­ based knowledge management tool designed to store and The Fire Effects Information System (FEIS) is a provide easy access to up-to-date information on the ef­ computer-based, menu-driven encyclopedia offire effects fects of fire and general ecology of plant species, wildlife and general ecological information for plant species, wild­ species, and plant communities. Information is stored in life species, and plant communities. It provides interpret­ the knowledge base as readable text providing a one-step ed, summarized information in an easy-to-use format and process for information retrieval. This is in contrast to will soon be available at any location with computer-to­ simple on-line citation retrieval systems where the user computer communication capabilities. When fully opera­ is still obliged to request and receive pertinent articles tional, FEIS will be national in scope. At present its main and sift through them for useful information. emphasis is on aridland shrubs and associated vegetation. New information is being added on a continuing basis. A list of FEIS contents to date and a sample output are SYSTEM DESCRIPTION included. FEIS has three basic components: the "Builder," the "Query," and the knowledge base. The Builder is the INTRODUCTION program used to enter new information or to edit and update text already entered. Access to the Builder is Forums such as the Wildland Shrub Symposium can limited to biologists or other professionals with there­ provide a valuable means of transmitting scientific infor­ sponsibility of maintaining the knowledge base (at pres­ mation to interested parties. However, important as they ent, these individuals are all Forest Service employees are, they reach only a limited audience. A larger number or cooperators stationed at the Intermountain Fire Sci­ of people may obtain information directly from scientific ences Laboratory, Missoula, MT). Putting information journal papers or through published summaries of re­ into the FEIS requires: (I) making a thorough bibliogra­ search literature or symposia proceedings. In theory, the phic search to identify relevant literature; (2) obtaining literature is accessible to all researchers and managers. the literature; (3) reading and evaluating the reliability The reality is not so simple, particularly for professionals of the literature received; (4) resolving conflicts, where involved in shrubland management. Many managers are possible, between contradictory pieces of information; stationed in isolated areas where access to research re­ (5) synthesizing the information in a written report; sults is slow or difficult. They have only limited time to (6) obtaining review comments from coworkers, supervi­ spend searching for and obtaining publications because sors, and the copy editor; (7) obtaining outside technical of the press of other duties. Research scientists them­ review from recognized experts; and (8) entry of the infor­ selves are finding it more and more challenging to keep mation into the knowledge base. up with the huge volume of reports published each year The Query provides viewing access to all users. The in literally hundreds ofjournals. A frustrating commu­ Query is menu-driven and no special knowledge of com­ nications gap exists between those who do research and puters or their operation is required to run the program. those who want to apply it effectively. On~ method of Users may scan text on a computer screen or request a bridging this gap is to make use of the current trend in file to be printed at their home stations. They are not rapid development and dissemination of computer tech­ able to alter the knowledge base using this program. nology to even the· most remote locations. The knowledge base contains all information input A collaborative effort between the Intermountain Re­ using the Builder, as well as some of the Builder and search Station's Intermountain Fire Sciences Laboratory Query program structural organization. The information and the Computer Science Department of the University in the FEIS is organized in a tree-like hierarchy (fig. 1). of Montana was initiated to develop a way to use com­ A user begins a search at the "root" of the inverted tree puter technology to deliver meaningful information more by making an initial decision to view information in one effectively. The result of this collaboration is the Fire of three basic categories: plant species, wildlife species, or ecosystem. The species or ecosystem of interest may be chosen from a menu of common and scientific names, Paper presented at the Symposium on Cheatgrass Invasion, Shrub Die­ or may be accessed by typing in the scientific name or a Off, and Other Aspects of Shrub Biology and Management, Las Vegas, NV, six- or seven-letter abbreviation (see appendix A). Plant April 5-7, 1989. Anne F. Bradley is an Ecologist, Intermountain Research Station, taxonomic nomenclature changes at intervals and the Forest Service, U.S. Department of Agriculture, Intermountain Fire system permits access to a number of species by more Sciences Laboratory, Missoula, MT 59807. 263 This file was created by scanning the printed publication. Errors identified by the software have been corrected; however, some errors may remain. LEGEND: 0 FRAME / RELATIONSHIP (COMPONENT LINK) «0 MULTIPLE OCCURRENCES OF FRAMES OF THE SAME TYPE AND SUBSTRUCTURE Figure 1-Structure of fire effects information system. than one name. For example, information on bluebunch managing particular species or ecosystems have insights wheatgrass may be accessed by using the name Agropyron that can help their successors do a better job. Their valu­ spicatum or the more recent designation Pseudoroegneria able insights can be integrated into the system informa­ spicata. Information on each species or ecosystem is sub­ tion. For example, the Case Studies section in the Fire divided into topical areas. For example, the plant species Effects topical area (Appendix B) can potentially provide category contains information on plant distribution and a place to record the conditions that lead to successful fire occurrence, value and use, general botanical characteris­ application in different communities, whether this infor­ tics,· adaptations to fire, and fire effects. Each of these mation resides in the published literature or not. topical areas is further subdivided. Within the general The system is written in contmon LISP programming botanical and ecological characteristics topical area, one language. This language afforded greater flexibility may view a general text description of the plant's mor­ than others during program development because of phology and ecology, plant regeneration, site characteris­ some unique characteristics. Coded functions are inter­ tics, successional status, seasonal development, and a preted rather than compiled, allowing them to be tested characterization of the species using the lifeform classifi­ individually before being incorporated into the main pro­ cations developed by Raunkiaer (1934). An example of gram structure. Unlike FORTRAN and COBOL, a pro­ FEIS output is included in appendix B. grammer does not have to specify in advance the sizes All topical areas include a list of cited references. This and types of data to be handled. We found this to be a is an important feature, permitting the user to locate the useful feature as the scope of the FEIS project evolved. original source material if more detailed information is FEIS is an object-oriented, frame-based, knowledge-based needed. Complete citations of the literature used for each system. For those interested, further discussion of FEIS species or ecosystem summary are stored in a separate structure and development may be found in Fischer and computer bibliographi~ file that will also be accessible to Wright (1987). users when the system is fully implemented. The same knowledge base is accessed by both the Builder and the Query so that any updates made to the system are imme­ POTENTIAL USES OF THE SYSTEM diately available to users. Information in the system at Although the program's main focus is the effects of fire present is current to 1986 or later, depending on the on species or ecosystems, much of the information is ap­ species. plicable to other resource management needs. During FEIS has the unique potential to "capture" good in­ early development of the program, the prototype system formation that is rarely published in the scientific lit­ was demonstrated at several dozen field locations in erature. Professionals who have spent their careers Arizona, Idaho, Nevada, Oregon, South Dakota, and 264 Utah. The participants listed the following potential SYSTEM STATUS uses ofFEIS: To date, the FEIS prototype system contains infor­ prescribed fire plans mation on 212 plant species, predominantly those that fire rehabilitation plans occur in arid shrublands. Also included are descriptions escaped fire analysis of 10 sagebrush cover types and eight wildlife species. land use plans Appendix A includes the current species list. A break­ exotic species control plans down of plant species lifeform by ecosystem is presented environmental assessments and impact statements in table 1. More entries are being made on a continuing vegetation management plans (range, wildlife basis. habitat, and silvicultural prescriptions) The prototype is being tested by managers

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    19 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us