Marsh bird survey data management
Download
1 / 9

Marsh Bird Survey Data Management - PowerPoint PPT Presentation


  • 82 Views
  • Uploaded on

Marsh Bird Survey Data Management. Marsh Bird Monitoring Technical Workshop March 6-8, 2006. USFWS Refuges Database Development Project. SSP project with Patuxent to develop biological databases for Refuges data management system

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Marsh Bird Survey Data Management' - elina


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Marsh bird survey data management

Marsh Bird Survey Data Management

Marsh Bird Monitoring Technical Workshop

March 6-8, 2006


Usfws refuges database development project
USFWS Refuges Database Development Project

  • SSP project with Patuxent to develop biological databases for Refuges data management system

    • Point Count Database: Modified to meet Refuges requirements and maintain other users

    • Develop data management system for Marsh Bird surveys conducted on Refuges


Usfws refuges database development project1
USFWS Refuges Database Development Project

  • Marsh Bird Survey Data Management System Development:

    • User Acceptance Team (UAT) established in autumn 2005

    • Started developing system requirements in January 2006

      • Data stored in modified Point Count Database

      • New web interfaces developed specifically for Marsh Bird Surveys

    • Anticipated functional system: Autumn 2006


Conceptual data management system
Conceptual Data Management System

  • Centralized data management system with dispersed responsibilities for data management

    • Individual “programs” responsible for assigning management functions and ensuring data quality

    • “One-time” importation of existing data sets


Conceptual data management system contd
Conceptual Data Management System, contd.

  • Web-based data entry process

    • Embedded QA/QC functions to reduce entry errors

    • Individual “programs” responsible for own data entry

      • All data entered electronically

    • Marsh bird survey data stored in data tables within Point Count database


Conceptual data management system contd1
Conceptual Data Management System, contd.

  • Editing functions accomplished via Internet

    • Individual “programs” responsible for editing own data sets

    • Access to data restricted until editing process is completed

    • After editing is completed, changes to these data are tracked by the database


Conceptual data management system contd2
Conceptual Data Management System, contd.

  • Proofed data are accessible via Internet

    • Access to proprietary data can be restricted by “programs”

  • Queries and data summaries will be customized to meet specifics of marsh bird survey data

  • Small datasets provided immediately; large datasets available via FTP


Window of opportunity
Window of Opportunity

  • Build upon Refuges Marsh Bird Data Management System to produce a system that supports an operational survey program

    • PWRC is willing to commit “available resources” (=programmer’s time) to expand and maintain Refuges system to meet reasonable needs of operational continental program

      • Timing should to follow closely upon/with development of Refuges system


Data management issues
Data Management Issues

  • Should this group be talking about data management at this time?

  • Is the Refuges data management model reasonable for a continental program?

  • Can additional system requirements be identified at this time?

    • Should system be centralized or distributed?

      • Should U.S. and Canada maintain separate systems?

      • How to interface with national/regional programs?

    • Metadata considerations with respect to individual programs

  • Are there issues with proprietary use that may restrict access to these data?


ad