Laserfiche WebLink
<br />l <br /> <br />COLORADO RiVER RECOVERY PROGRAM <br />FY 02 ANNUAL PROJECT REPORT <br /> <br />RECOVERY PROGRAM <br />PROJECT NUMBER: 16 <br /> <br />1. Project Title: Database Management Program and Interagency Standardized <br />Monitoring Program. <br /> <br />11. Principallnvestigator(s): <br /> <br />Charles W. McAda, Project Leader <br /> <br />764 Horizon Drive, Building B <br />Grand Junction, Colorado 8 I 506 <br />(970) 245-9319; FAX 245-6933 <br />chuck _ mcada@fws.gov <br /> <br />III. Project Summary: <br /> <br />Development ofa centralized database was a requirement of the Recovery Program <br />when it was formed in 1986. All researchers who receive funding through the <br />Recovery Program are required to submit all fishery data to the central database at the <br />completion of their study. In addition, all researchers are required to submit a <br />complete list of all endangered fish handled each year to the central database. <br />Guidelines for the annual tagging list are circulated to researchers each year. A <br />consolidated tagging list is compiled and distributed after tagging data are received <br />from all researchers. <br /> <br />Most of the UCRB database consists of the 'all fish' data collected during the <br />different investigations funded by the Recovery Program. These data relate to <br />species, number collection date, site, gear, effort expended, habitat and any other <br />parameter associated with collection of that fish. Only field fish-collection data or <br />radiotelemetry data are required to be submitted. The Recovery Program does not <br />require submitting data from invertebrate, geomorphology, hatchery or laboratory <br />studies. All fishery data associated with a study are due to the database when the <br />final report is approved by the Recovery Program. <br /> <br />All data are stored in individual dBASE files according to project and year(s) of <br />collection. Data are not combined into one large database because of the wide variety <br />of studies and study designs used. A list of field names and data codes has been <br />prepared to guide database development. Investigators who use dBASE and field <br />names and codes from the list do not need to provide any further documentation about <br />the data file. However, any fields not described in the List ofField Names m.ust be <br />fully documented when the file is submitted. Because of the wide variety of study <br />designs file structures vary widely, but all data of the same type are contained in <br />fields with the same name and structure (e. g. the river where sampling occurred is <br />identified by the same two-digit code in a field named 'RIVER'). Investigators may <br /> <br />FY 2002 Annual Report 16 Page - 1 <br />