Difference between revisions of "Products and Services"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
==Monthly Teleconference== | ==Monthly Teleconference== | ||
− | |||
− | |||
===Next call=== | ===Next call=== | ||
Line 8: | Line 6: | ||
====Discussion topics:==== | ====Discussion topics:==== | ||
− | # | + | # Review past Committee activities |
− | # | + | # Update Committee goals and objectives based on participant interests |
+ | # Plan for the Summer ESIP Meeting (e.g., a Metadata Fair?) | ||
+ | # Select a Committee Vice-Chair | ||
+ | # Identify permanent telecon day/time | ||
− | ==Issues | + | |
− | : | + | ==Issues of interest to the Products and Service Standing Committee== |
+ | Potential topics: | ||
+ | # Deficiencies of current metadata standards: ISO 19115, OGC WMS/WCS/WFS | ||
+ | # Improving metadata compliance | ||
+ | # Metadata for data quality, services, and provenance | ||
+ | # Representation of versioning | ||
+ | # Permanent dataset names, parameter names, registries, and identifiers | ||
+ | # Use cases for general ESIP usage | ||
+ | # Metadata harvesting and exchange and associated catalog services | ||
+ | # Client access to catalogs | ||
+ | # Service quality | ||
+ | |||
+ | Prior topics: | ||
:[[P&S Data Quality|Data Quality]] | :[[P&S Data Quality|Data Quality]] | ||
:[[P&S Avoiding Duplicate Metadata Records|Avoiding Duplicate Metadata Records]] | :[[P&S Avoiding Duplicate Metadata Records|Avoiding Duplicate Metadata Records]] | ||
:[[Federation Inventory]] | :[[Federation Inventory]] | ||
+ | |||
+ | |||
+ | |||
+ | == Reference Documents == | ||
+ | Air Quality Metadata Use Case: | ||
+ | https://sites.google.com/site/geosspilot2/air-quality-and-health-working-group/aq-community-catalog---publish-register-harvest | ||
+ | |||
==Past Discussions: == | ==Past Discussions: == | ||
Line 23: | Line 43: | ||
:[[P&S Monthly March 28, 2006]] | :[[P&S Monthly March 28, 2006]] | ||
− | |||
− | + | ==Purpose of Products and Services Committee - from ESIP Bylaws== | |
:a. To encourage the development, use and improvement of best science practices to ensure the quality, usability, and breadth of data and resultant information, products, and services; | :a. To encourage the development, use and improvement of best science practices to ensure the quality, usability, and breadth of data and resultant information, products, and services; |
Revision as of 22:50, February 23, 2009
Monthly Teleconference
Next call
- Tuesday, Feb 24, 2009, 3 PM EST
- 800-508-7631 Access Code: *1297219*
Discussion topics:
- Review past Committee activities
- Update Committee goals and objectives based on participant interests
- Plan for the Summer ESIP Meeting (e.g., a Metadata Fair?)
- Select a Committee Vice-Chair
- Identify permanent telecon day/time
Issues of interest to the Products and Service Standing Committee
Potential topics:
- Deficiencies of current metadata standards: ISO 19115, OGC WMS/WCS/WFS
- Improving metadata compliance
- Metadata for data quality, services, and provenance
- Representation of versioning
- Permanent dataset names, parameter names, registries, and identifiers
- Use cases for general ESIP usage
- Metadata harvesting and exchange and associated catalog services
- Client access to catalogs
- Service quality
Prior topics:
Reference Documents
Air Quality Metadata Use Case: https://sites.google.com/site/geosspilot2/air-quality-and-health-working-group/aq-community-catalog---publish-register-harvest
Past Discussions:
- P&S Monthly August 29, 2006
- P&S Monthly May 23, 2006
- P&S Monthly April 25, 2006
- P&S Monthly March 28, 2006
Purpose of Products and Services Committee - from ESIP Bylaws
- a. To encourage the development, use and improvement of best science practices to ensure the quality, usability, and breadth of data and resultant information, products, and services;
- b. To provide a Federation-wide forum for defining, developing and evaluating requirements for Federation Earth science products; and
- c. To provide a Federation-wide forum for defining, developing and evaluating requirements for product services and user services.