58
01101100 10101101 11101100 (AED, EMAP)
0110
1100
1010110111101100
(AED, EMAP)
0110
1100
10101101
11101100
10011011
(AED, EMAP)
0110
1100
1010
1101
111011000110
1100
1010
1101
11101100
(AED, EMAP)
0110
1100
1010
1101
111011000110
1100
1010
1101
11101100
(AED, EMAP)
(AED, EMAP)
Data Policy and Information Management Planning
Linda Harwell
US EPA/ORD/NHEERL/GED
“The overall purpose of these policy statements is to facilitate full and open access and use with confidence, both now and in the future, of the data and information . . .”
(Hale, et. al., June, 1999)
Piecing Together Your Plan
ObjectivesObjectives
Key Points
What are the policy/plan objectives? How will the data policy support
program objectives? What “type” of data will be
contributed? Who is the most likely audience? What are the partnership roles and
responsibilities?
EMAP IM Plan Objectives Providing a data directory so that data of interest can be
identified Providing access to data and metadata files Assisting with database development and/or
administration Providing support to EMAP working groups for planning,
research, monitoring, and analysis efforts so that differences in information management environments of the groups are minimized
Ensuring a distributed data structure, allowing responsibility for the data to reside with the owners
Maximizing interoperability with other environmental monitoring data systems in accordance with CENR objectives
Supporting Program Objectives . . .
. . . Is vital to the “health” of your IM program
Data Expectations
Data sets
Documentation of data sets
Statistical methods
Methodology for evaluating data
Reports
Spatial data
Other derived products
Data ownership/stewardship
Target Audience
Identify the primary user
Use “simple” language
Plan for training (i.e. workshops)
Provide guidance
Understand the user’s IM culture
Role and Responsibilities
Outline What needs to be done Who will do it
Provide reasonable expectations for all partners
Clear definitions help minimize misunderstandings and delays
* Two separate data fields
MD00-0053 NC00-0008
XCM0159 NC00-008
MD-CB-51 NC00008
MDCB-51 NC0008 BNT00
FishT_013 NC-08-C2000
13 BTRW* NC-08
MDT013 NC-00008
We’re supposed to enter the field data!?
What Role Are You Willing to Play?
Just a little inconsistency here
Go Ahead and Spell It Out
ObjectivesObjectives Technical Technical SpecificationsSpecifications
Piecing Together Your Plan
Key Points
How should the data flow? What hardware/software
should be used? What tools should be made
available to partners? What are resource needs?
EMAP IM Information Flow
Data Relationships
EMAP IM Distributed System Components
The Nuts and Bolts
Other Considerations
Software limitations Email attachments Available software
Internet protocols and firewalls Network Contraints
T1 vs. frational Computers and operating systems
Current and future expertise needs
Archive and Recovery PlanD
ata
Sou
rces
EMAP IM
Redundant Backup
EPA/NHEERL/RTP
Natio
nal A
rchives
Reco
rds A
dm
in(E
PA
Directive 2100)
ObjectivesObjectives
ImplementationImplementation
Technical Technical SpecificationsSpecifications
Piecing Together Your Plan
Recommendations and Guidelines
Quality assurance/control
Preparation and delivery of data
Data distribution for public use
Providing “tools” help ensure you get what you need -- when you need it
SurveyExpected # of Samples
WaterQualityVisits
Group 1
Group 2
Group 3
56 54 54 39
35 35 32 31
37 34 2 35
Sediment
Collection
Visits
TrawlVisits
Intended Actual
QA Assessment ExampleCompleteness Check
QA Assessment Example
Reasonable Outliers
QA Assessment Example
Assessing Lab QA
Metadata CollectionGünther, 1998
Data Storage
DataAnalysis
Data Capture
Dat
a A
gg
reg
atio
n
Met
adat
a A
gg
reg
atio
n
Navigation and Info Retrieval
(State)
(NCADC)
“Raw” Vs. “Synthesized” Data
Transactional Vs. Reduced
Sediment ChemSediment ChemTissue ChemTissue ChemWater ChemWater ChemSediment CompSediment CompQuality AssuranceQuality Assurance
Sediment ToxicitySediment ToxicityQuality AssuranceQuality AssuranceControlsControls
OrOr
OrOr
Chemistry TableChemistry Table
Sediment Toxicity Sediment Toxicity Results TableResults Table
One Big File Vs. Subsets of Data
Data Transfer Format
Purpose
Required
Optional
Standards
Public Data Distribution
Data View Options
Data View Options
Data Download Format
Tab-delimited ASCII Query Result
Data Sharing
Oregon Small EstuariesSediment Toxicity Tests - A. abdita
0102030405060708090
100110
50 60 70 80 90 100 110
% Control-Corrected Survival
Pe
rce
nt
Are
a
HA !HA !
HA !HA !HA !HA !
Analysis Tips –Making Friends and Influencing People
What was the primary study question?
What are the recommended methods of analyses?
How else can these data be used?
Oregon Small EstuariesSediment Toxicity Tests - A. abdita
0102030405060708090
100110
50 60 70 80 90 100 110
% Control-Corrected Survival
Pe
rce
nt
Are
a
Oregon Small EstuariesSediment Toxicity Tests - A. abdita
0102030405060708090
100110
50 60 70 80 90 100 110
% Control-Corrected Survival
Pe
rce
nt
Are
a
Joys of Metadata
Metadata Formats
EMLFGDC
NBII
Metadata Tools
Metadata Consultants
EMAP Example
Data Directory
Data Catalog
EPA’s EIMS
Frithsen and Shepanek; 1998,2000
ObjectivesObjectives
ImplementationImplementationPlanning Planning for the for the FutureFuture
Technical Technical SpecificationsSpecifications
Piecing Together Your Plan
What Does the Future Look Like?
Continue to meet program needs Accommodating program evolution
How might users’ needs change Keep up with emerging technology
Resources Expertise
What will it take to:
Evolution of EMAP
Highly Centralized andCompartmentalized
Multi-scaled, DiversifiedCoordination Effort
Staying Afloat
Be prepared to revise IM policy and plan
Make connections with other programs
Proactively work IM plan Make excerpts a part of QAPPs
Information Management PlanEaGLe
Data for the Next Generation
Coming Soon: 2003