Provenance Context Content Standard Use Case with Physical Objects
-
Upload
denise-hills -
Category
Technology
-
view
316 -
download
0
description
Transcript of Provenance Context Content Standard Use Case with Physical Objects
Applying the Emerging PCCS to Physical Objects in
a Core RepositoryA Use Case to Demonstrate Validity of
Broader Community Adaptation
Denise J. Hills, Geological Survey of AlabamaSarah Ramdeen, UNC-Chapel Hill SILS
H. K. Ramapriyan, NASA Goddard Space Flight Center
AGU Annual Meeting
Data sets prepared and/or preserved with community-accepted data management standards are more likely to be used, now and in the future
Standards developed using suggestions and assessments by a diverse community enable wider adoption without necessarily needing customization
9 December 2013
Why Community Standards?
AGU Annual Meeting
ESIP Federation’s Data Stewardship Committee developed the PCCS matrix based on community input
Focus is on “what” needs to be preserved, rather than “how”
Developed primarily with NASA/NOAA remote-sensing missions in mind, but meant to be easily adapted to other Earth Science data sets
Current matrix has 8 high-level categories
9 December 2013
Provenance and Context Content Standard (PCCS)
AGU Annual Meeting
PCCS High Level Categories1) Preflight/Pre-Operations2) Products (Data and
Metadata)3) Product Documentation4) Mission Calibration
5) Product Software6) Algorithm Input7) Validation8) Software Tools
9 December 2013
AGU Annual Meeting
PCCS – Content Attributes Content name More detailed definition
and description Indication of why the
item needs to be preserved
Criteria for quality assessment
Priority for preservation of the item
Source of the content item during the data life cycle
Project phase for capturing the item
9 December 2013
AGU Annual Meeting
An approach to develop or refine the functional specifications of a system
Intended to be characteristic of classes of scenarios, although specific real-world examples may enable fuller understanding of strengths and weaknesses of what is being tested
Should attempt to cover the full “data life cycle”
9 December 2013
About Use Cases
AGU Annual Meeting
9 December 2013
Data Life Cycle
http://www.dataone.org - DataONE Best Practices Primer
AGU Annual Meeting
Geological Survey of Alabama (GSA) houses cores, cuttings, and other physical samples collected from oil and gas wells drilled in the state
Repository also contains samples from other states (e.g., when they de-ascension items), and from non-energy wells (e.g., drilled solely for research)
9 December 2013
Use Case: Applying PCCS to a Core Repository
AGU Annual Meeting
Core Warehouse
9 December 2013
AGU Annual Meeting
As a state agency, part of our mission is to make data available to the public
GSA has not yet standardized records relating to physical samples, making data discovery difficult
As with many other agencies, there is limited funding for preservation efforts so GSA must be strategic
9 December 2013
Why is GSA interested?
AGU Annual Meeting
Preservation of Core
9 December 2013
AGU Annual Meeting
Better use of resourcesTimeMoneyTraining
Interoperability (and therefore potential for data use and reuse) increases
Discoverability increases with standardization
9 December 2013
Motivation for GSA to utilize PCCS
AGU Annual Meeting
Spreadsheets containing basic informationAssociated O&G well (always)Location in TRS format (always)Type of sample (usually) Internal sample number (sometimes)Footage and/or unit sampled (occasionally)Date acquired (rarely)Related resources (rarely)
9 December 2013
Core Repository Documentation Available
AGU Annual Meeting
From the associated O&G well:Location in Lat/Long NAD1927 (almost always)Operator information (always)Permitting information, including drilling, logging,
and completion dates (almost always)Well TD (almost always)Drilling logs (sometimes)
Can often get sample depths from the drilling logRelated resources (sometimes)
Core analyses can give further information on units
9 December 2013
Core Repository Documentation Available
Mapping PCCS High Level Categories to Physical Samples
Current Category
1) Preflight/Pre-Operations
2) Product Data and Metadata
3) Documentation4) Calibration
PhysObj Category
1) Site selection/predrilling
2) Product Data 3) Documentation and
Metadata4) Recovery
information*
AGU Annual Meeting 9 December 2013
Mapping PCCS High Level Categories to Physical Samples
Current Category
5) Product Software6) Algorithm Input7) Validation8) Software Tools
PhysObj Category
5) Not Applicable*6) Conventions7) Not Applicable*8) Not Applicable*
AGU Annual Meeting 9 December 2013
AGU Annual Meeting
Example PhysObj Content Attributes – Site Selection
Content name Permitting
Definition and description Permit application with
associated documentation Why the item needs to be
preserved Resource information about
area QA of content
Complete and accurate form
Priority for preservation High
Source of the content item during the data life cycle Well owner/operator
Project phase for capturing the item Pre-operational
9 December 2013
AGU Annual Meeting
Example PhysObj Content Attributes – Data and Metadata
Content name Core Sample | Subsample
Definition and description Physical object collected
Why the item needs to be preserved Without the object
analyses cannot be done QA of content
Preservation standards
Priority for preservation High
Source of the content item during the data life cycle Well owner/operator
(initial) | Repository (post-ascension)
Project phase for capturing the item Post-drilling
9 December 2013
AGU Annual Meeting
Example PhysObj Content Attributes – Documentation
Content name Metadata
Definition and description Includes location, depth of
measurement, techniques Why the item needs to be
preserved Provenance critical
QA of content Comparison to robust
metadata content model standards
Priority for preservation High
Source of the content item during the data life cycle Well owner/operator
(initial) | Regulatory agency (initial) |Repository (post-ascension)
Project phase for capturing the item During drilling (collection)
9 December 2013
AGU Annual Meeting
Categories in the PCCS that do not currently have a clearly identified physical object counterpart (e.g., Calibration; Validation) need further examination:Has the item not been captured in the current
repository, but should be?Has the item been captured, but not identified yet
within the information available? Is there a more universal description of the
content category?
9 December 2013
Future Work
AGU Annual Meeting
Additional examination of category mapping on a more detailed level is needed to fully define each content item
PCCS should be applied to additional physical repositories (additional use cases)Ask us how!
9 December 2013
Future Work
AGU Annual Meeting
The Data Preservation Committee of the ESIP Federation was fundamental to the development of the material presented.
9 December 2013
Acknowledgements
AGU Annual Meeting
9 December 2013
Connecting Data Stakeholders for a Long-term Vision of Data
Stewardship
TOWN HALLMonday, 6:15-7:15pmMoscone South 306