Infrastructure to Support Integration and Dissemination

1
Infrastructure to SupportIntegration and
Dissemination
Inventory Monitoring Program

• National Park Service
• Inventory Monitoring Program
• Presented by
• Dorothy Mortenson (SWAN)

2
Whats Infrastructure?

• Refers to the network of computers and servers
  that our information systems are built upon.
  DMPs
• It should support the development, repository,
  integration, interaction and dissemination of IM
  Program and Park data.

3
Basic Principles

• Separate Testing/Development from Production
• Separate in-house vs. public
• Separate dynamic vs. static
• Separate process intensive vs. non-intensive

4
Types of Servers
5
What does this mean when it comes to integration?

• Product Integration
• Multi-disciplinary/multi-source integration for
  analysis

6
Product Integration
One report integrates with other reports One
season of WQ data integrates with other WQ data
Review Product File Server (Work)
Post to Repository File Server (digital library)
Document Catalog Database Server
Data Discovery Application/Internet Server
Distribution File Server (digital library)
Use File Server (Work)
7
Multi-disciplinary and -source Integration for
Analysis
NON-Program Sources Database Server
NON-Program Sources Request for Download
Application Server
Subset Data NPS Database Server
Analysis Application, Database, and/or File
Server
8
Potential infrastructure hurdles

• NPS policies on web development
• Access to database server MS SQL Server vs Oracle
• Resources available database administrator,
  assistance in web development
• Uploading/downloading large quantities of data
• Consistent requests to non-NPS sources

9
(No Transcript)
10
Considerations

• Identify specific data needs
• Identify clearinghouses for all products and
  vital signs data. Diagram start to finish.
• Does the finish reach the public in some way?
• Which direction is the flow of data going?
• Which is the master which is the subset?
• Is the proposed Clearinghouse/Repository up for
  the task?
• Where do you have or have no control/input?

11
Considerations

• Database servers require expertise and resources
  to manage look for means for sharing
• Database servers require higher level of data
  standards have a good design from the start
• Application development takes time and is only as
  good as defined user requirements

12
Discussions for Data Managers

• NPS policies on web development
• Backup plan if web access is cut off
• Explore server options SQL Server vs Oracle
  WASO, regional, network or park
• Test application/database development on intranet
• Pool resources for DB admin/Web development

13
Discussions for Data Managers

• Identify how master datasets will be handled
• Identify how subsets will be handled
  (export/import)
• Minimum requirements for non-NPS partner
  repositories ( concept to vouchers loans)
• Use common or compatible non-NPS partner
  repositories, if possible (build momentum)
• Forum on inside.nps.gov/forum list your concerns

14
NPS IM Model and Examples

• Progress being made for NPS clearinghouses - Joe
  Gregson