NRDT Version 3

1
NRDT Version 3

• An Improved Model for IM Natural Resource
  Databases

Inventory and Monitoring Program
2
NRDT A Brief History

• Fall 2001
• NRDT development begins
• Develop Phase 1
• Spring 2002
• Beta test Phase 1
• Develop and release Phase 2
• Fall 2004
• Functional reassessment of Phase 2
• Draft Version 3 for review and comment

3
NRDT User Survey

• Sent to all DMs
• Questions about
• Primary key structure
• Appropriateness of Phase 2 database structure
• Need for integration with GIS
• Need for a data transfer/export standard
• Most important vital signs being studied
• Desired tools and functionality for NRDT
• Need for a NRDT mandate from IM

4
Functional Reassessment

• Phase 2 NRDT User Survey Results
• Primary key structure was not optimal
• Core relationships didnt model the majority of
  field sampling protocols
• Therefore, interface design (forms, queries,
  reports, etc.) unnecessarily difficult
• Not clear how to integrate with GIS

5
NRDT Revision Team

• NRDT Revision Team formed to assess issues and
  provide redesign expertise
• Seven IM data managers (new and experienced)
• Three IM program analysts
• Seven networks from across the NPS
• Professional backgrounds
• Computer Information Systems
• Geographic Information Systems
• Ecology

6
NRDT Revision Team

• Rose Cook - Sierra Nevada IM Network
• Chris Dietrich - IM Washington Service Office
  (Fort Collins)
• Joe Gregson - IM Washington Service Office (Fort
  Collins)
• Mark Hart - Great Lakes IM Network
• Susan Huse - Northeast Coastal Barrier IM
  Network
• Lisa Nelson - IM Washington Service Office (Fort
  Collins)
• Velma Potash - Northeast Coastal Barrier IM
  Network
• Gareth Rowell - Heartland IM Network
• Brian Witcher - South Florida/Carribbean IM
  Network
• Christina Wright - Southeast Coast IM Network

7
Revision Team Guiding Principals

• Legacy databases should not need to be changed
• An improved single model that better matches the
  most common field protocols
• An extendable core that is well-designed and
  optimized for ease of interface design
• Facilitate connection to GIS applications
• Anticipate the need for data integration/roll-up
  at park, network and regional levels

Inventory and Monitoring Program
8
Phase 2 Model
Core Tables
Protocol-specific Tables
9
Version 3 Core

• Backwards compatibility with Phase 2 databases
• Optimized for the majority of protocols
• Simplifies core table relationships
• Simplifies interface design
• Provides first-tier common tables/fields
  necessary for data integration/roll-up
• Formalizes link(s) to GIS
• Adds metadata component

10
Version 3 Core Model
Protocol-specific Tables
Core Tables
Metadata
11
Version 3 Extended Core

• Provides tables, fields and relationships to
  handle second-tier commonalities
• Provides the flexibility needed the model all
  field sampling protocols

12
Version 3 Extended Core
Protocol-specific Tables
Extended Core Tables
Metadata
13
Version 3 Data Locations

• Incidental, opportunistic or data point locations

14
NRDT as a Development Platform

• DM-vetted data model
• Rapid application development
• Customization is expected/necessary

15
NRDT as a Data Exchange Standard

• Program-wide standardization
• Data roll-up (park/network/region-level)
• Benefits DM/developer

16
NRDT GIS Integration

• GIS_Location_ID
• tbl_Sites
• tbl_Locations
• tbl_Data_Locations
• Conforms to already established NPS GISC
  standards

17
Version 3 Data Sharing

• Primary key issues resolved in a way that
  facilitates data sharing and integration
• GUIDs create unique record identifiers for shared
  data

18
Version 3 Integration

• Improved integration with other IM data systems
• Dataset Catalog metadata
• NR/GIS Data Store metadata
• NP Species taxonomic lookup tables and species
  evidence
• Theme Manager Arc-To-Access GIS
  integration/spatial data analysis

19
Version 3 GIS Functionality

• Issues with location resolved in a way that
  facilitates integration with GIS
• Formalized link to GIS features
• Conforms to already established NPS GISC
  standards

20
Version 3 Status

• A formal NRDT v3 review was conducted in December
  2004
• Naming convention was sent out for service-wide
  review January 2005
• New NRDT v3 application development began in
  early 2005
• NRDT Standards Committee began work again in
  January 2005

21
NRDT v3 Rapid Application Development

• Additional (Extended Core) tables
• Plug and play tables for second-tier
  commonalities
• NRDT Data Standards
• Facilitate rapid NRDT application development
• Table/field naming convention
• Promotes service-wide consistency
• New DMs ramp-up quickly
• Example NRDT v3 applications
• NERO model conversion SOP for adding protocols
• NCCN model and developer SOP
• SODN model implementing many v3 features

22
NRDT Resources

• NRDT Examples webpage
• http//science.nature.nps.gov/im/apps/template/NRD
  TExampleApplications.htm
• NRDT Standards webpage
• http//science.nature.nps.gov/im/apps/template/Dat
  aStandards.htm
• NRDT webpage
• http//science.nature.nps.gov/im/apps/template/ind
  ex.htm

23
NRDT Application Demonstrations

• Patrick Flaherty
• APHN Fish
• Alan Williams
• SHEN
• Mark Hart
• GLKN geodatabase

• Velma Decker
• NCBN
• Andrew Duff
• KLMN NR Database
• Doug Wilder
• CEAN mobile computing

24
NRDT Examples

• ftp//63.220.43.40/
• \NRDTExamples\
• Login npsftpwin
• PW FTP04npswin

25
NRDT Example Themes

• Coordinate data
• In tbl_Locations
• Location_Type
• Separate table (1many)
• tbl_Data_Locations
• tbl_Dead_Saguaros
• Lookup tables
• Distributed taxonomy
• Centralized taxonomy, observers, project mgt.
• Consolidated enumeration table(s)

26
NRDT Example Themes

• Primary Keys
• AutoNumbers (Access default)
• GUID (w/concatenated string)
• GIS
• Arc2Access (Alaska) display, query
• Geodatabase data entry/edit?
• Documentation SOPs
• NCCN
• NERO/NCBN

27
NRDT Caveats

• Design flexibility
• Autonumbers, GUIDs, concat. strings
• Flexibility w/object names
• GIS Integration
• Data Standards
• Departures locally supported