Difference between revisions of "Desired Characteristics of Air Quality Data Systems"
From Earth Science Information Partners (ESIP)
Line 8: | Line 8: | ||
== Comments from Data Summit Workshop == | == Comments from Data Summit Workshop == | ||
=== Group A2: Enabling Data Access === | === Group A2: Enabling Data Access === | ||
− | + | '''Data system capabilities.''' These five information capabilities reflect the breakout’s sense of the capabilities that are foundational to enabling data access that either don’t exist or can be improved upon. An improved ‘system’ would: | |
# Making access to data the standard expectation for government funded data; | # Making access to data the standard expectation for government funded data; | ||
# Increase access to orphan or gray data ; | # Increase access to orphan or gray data ; | ||
Line 15: | Line 15: | ||
# Be robust and stable to so that application developers and their funders would be confident in relying on such a system, even though they do not own it; and | # Be robust and stable to so that application developers and their funders would be confident in relying on such a system, even though they do not own it; and | ||
# Be consistently described | # Be consistently described | ||
− | + | '''Principles:''' | |
* The system would assume that information is always accessible when data owners define appropriate, and ownership and stewardship responsibilities are established. This would include versioned and archived information. | * The system would assume that information is always accessible when data owners define appropriate, and ownership and stewardship responsibilities are established. This would include versioned and archived information. | ||
* The system will enable user feedback in all parts of Data Value Chain and be consistently described. | * The system will enable user feedback in all parts of Data Value Chain and be consistently described. | ||
* The system and its participants will adhere to a community defined and governed suite of standards/conventions. | * The system and its participants will adhere to a community defined and governed suite of standards/conventions. | ||
− | + | '''Community Actions:''' | |
* clarify ownership and stewardship responsibilities, | * clarify ownership and stewardship responsibilities, | ||
* must assure that when data is accessed credit is received when credit is due, , | * must assure that when data is accessed credit is received when credit is due, , | ||
Line 25: | Line 25: | ||
* establishing a standard mechanisms for data discovery and description | * establishing a standard mechanisms for data discovery and description | ||
* identifying what in the system can and should be standardized. | * identifying what in the system can and should be standardized. | ||
− | + | * Learn from the experience of partner who have been working these areas ahead of us. | |
== Related Links == | == Related Links == |
Revision as of 22:37, March 10, 2008
Back to < Community Air Quality Data Systems Strategy
Desired Characteristics of Air Quality Data Systems
Chapter text here.
Comments from Data Summit Workshop
Group A2: Enabling Data Access
Data system capabilities. These five information capabilities reflect the breakout’s sense of the capabilities that are foundational to enabling data access that either don’t exist or can be improved upon. An improved ‘system’ would:
- Making access to data the standard expectation for government funded data;
- Increase access to orphan or gray data ;
- Include new classes of data such as model outputs;
- Provide easy access to relevant archived/versioned data;
- Be robust and stable to so that application developers and their funders would be confident in relying on such a system, even though they do not own it; and
- Be consistently described
Principles:
- The system would assume that information is always accessible when data owners define appropriate, and ownership and stewardship responsibilities are established. This would include versioned and archived information.
- The system will enable user feedback in all parts of Data Value Chain and be consistently described.
- The system and its participants will adhere to a community defined and governed suite of standards/conventions.
Community Actions:
- clarify ownership and stewardship responsibilities,
- must assure that when data is accessed credit is received when credit is due, ,
- work as a community to define the expectation of data accessibility by type of data.
- establishing a standard mechanisms for data discovery and description
- identifying what in the system can and should be standardized.
- Learn from the experience of partner who have been working these areas ahead of us.