Data Management
Klamath Network Vital Sign Databases
The KLMN is making every attempt to use databases that have already been developed to obtain and store data collected from our monitoring projects. If a database is not available, we will adapt the Natural Resource Database Template (NRDT) developed by the National I&M Program staff to meet the needs of our projects. The NRDT is a core relational database structure that can be modified and built upon by different parks and networks, depending on the components of their inventory and monitoring programs and the specific sampling protocols they use (Washington Support Office, 2004).
In addition, the Network will work closely with the parks to determine what system, if any, they are utilizing to collect data that are similar to the data being gathered as part of our monitoring effort. While it is recognized that we will not be able to conform to all databases utilized by each park, the Network will make every attempt to utilize databases that are compatible with the park databases.
Listed below are the 10 Vital Sign Monitoring Projects the KLMN will be implementing, along with a brief description of the databases we plan on using to collect and store data as part of those monitoring projects.
Non-Native Species
Development of a standardized invasive plant database for the NPS is the ideal for easily sharing information about invasive species. However, this product is still in the planning stages while the NPS Natural Resource Program Center (NRPC) transitions data systems to a Service Oriented Architecture (SOA) and XML web services development approach for data management and delivery. After discussions with the NRPC staff, analyzing the data collection methods currently being implemented by the parks, and conversations with the several members of the Exotic Plant Management Teams (EPMT), we have decided to utilize the Weed Information Management System (WIMS) developed by The Nature Conservancy to collect data. This database is currently being adapted to meet all the needs of the Network and will be made available in the winter 2009. When the standardized database becomes available, the Network will determine if the database meets our needs and utilize the database if applicable.
Whitebark Pine
The Klamath Network has not selected a database for the project at this time. As we begin to develop the protocol for this project, we will work with the two park units where this protocol will be implemented and several other networks that are planning on monitoring whitebark pine to determine the best method to develop a database.
Terrestrial Vegetation
There are a variety of databases that have been developed to store and manage vegetation data by multiple agencies and organizations. The Klamath Network looked at several of these database but we were unable to find a database that could meet the majority of the needs of our project. Since we could not find a database that meets our needs, It was determined that we will developed a database using the Natural Resource Database Template (NRDT) developed by the National Park Service. A draft of this database will be made available in the Winter 2009. The database will contain automated reporting functionality, built-in quality control processes, complete documentation on the design and use of the database, and will meet all the needs of the lead ecologist.
Landbird Communities
The Network has entered into an agreement with the Klamath Bird Observatory (KBO) to implement our Landbird Communities Monitoring Project. KBO currently utilizes six relational databases and a series of SAS programs to collect, store, and quality control the data they collect. The Klamath Network is in the process of developing a relational database utilizing the NRDT and a bird monitoring database developed by the North Coast Cascades Network to use as part of our project. A draft of this database is expected to be completed by the spring of 2009.
Intertidal Communities
As part of a regional effort, the Klamath Network is monitoring three intertidal sites located at Redwood National Park. The data from these three sites are incorporated into the MARINe database. MARINe (Multi-Agency Rocky Intertidal Network) is a partnership of local, state, and federal agencies; universities; and private organizations monitoring 80 rocky intertidal sites along the coast of California and Oregon (core monitoring) and 91 sites over a broader area from Alaska to Mexico (biodiversity monitoring).
Water Quality and Aquatic Communities
The water quality component of the Natural Resource Challenge (NRC) requires networks to archive all physical, chemical, and biological water quality data collected with NRC water quality funds in the National Park Service's STORET database maintained by the NPS' Water Resources Division (WRD). Networks are encouraged to also archive any other aquatic-related data collected with base Vital Signs funding in STORET. To facilitate archiving NPS data in STORET, the WRD has developed a series of Access-based templates (called NPSTORET), patterned after the Natural Resource Data Templates, for networks to use to enter their water quality data in a STORET-compatible format. Networks will send their data from NPSTORET to the WRD on an annual basis for quality assurance and upload into the WRD's copy of STORET and the Environmental Protection Agency's (EPA) STORET National Data Warehouse.
Cave Entrance Communities and Cave Environments
The Klamath Network has not selected a database for this project. As we begin to develop the protocol for this project, we will work with the two park units where this protocol will be implemented and several other networks that are planning on monitoring cave ecosystems to determine the best method to collect and store data.
Land Cover
The Klamath Network has entered into an agreement with Southern Oregon University to provide GIS and Remote Sensing support for the Network. As we begin to develop our protocol, the Network will work closely with SOU, the park units within the Network, other networks, and the National I&M Staff to develop a data storage method for this protocol.