Difference between revisions of "User Requirement Registry"

Latest revision as of 13:52, October 26, 2010

< GEO User Requirements for Air Quality | Report | Documents | Resources

Erin: Make Dynamic List for GEO_URR Tags

</p><p><br /> </p> <div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none"/><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div> <ul> <li class="toclevel-1 tocsection-1"><a href="#User_Requirements_Registry_.28D._Niebert.2C_2009.29"><span class="tocnumber">1</span> <span class="toctext">User Requirements Registry (D. Niebert, 2009)</span></a> <ul> <li class="toclevel-2 tocsection-2"><a href="#URR_Administrative"><span class="tocnumber">1.1</span> <span class="toctext">URR Administrative</span></a></li> <li class="toclevel-2 tocsection-3"><a href="#User_Requirements_Registry_Features_.28Gary_Foley.29"><span class="tocnumber">1.2</span> <span class="toctext">User Requirements Registry Features (Gary Foley)</span></a></li> <li class="toclevel-2 tocsection-4"><a href="#User_Classes_for_Air_Quality_.28Gary_Foley.29"><span class="tocnumber">1.3</span> <span class="toctext">User Classes for Air Quality (Gary Foley)</span></a></li> </ul> </li> <li class="toclevel-1 tocsection-5"><a href="#Activities_of_Each_User_Class"><span class="tocnumber">2</span> <span class="toctext">Activities of Each User Class</span></a></li> <li class="toclevel-1 tocsection-6"><a href="#HP_Plag:"><span class="tocnumber">3</span> <span class="toctext">HP Plag:</span></a></li> <li class="toclevel-1 tocsection-7"><a href="#Activities"><span class="tocnumber">4</span> <span class="toctext">Activities</span></a></li> </ul> </div> <h2><span id="User_Requirements_Registry_(D._Niebert,_2009)"></span><span class="mw-headline" id="User_Requirements_Registry_.28D._Niebert.2C_2009.29">User Requirements Registry (D. Niebert, 2009)</span></h2> <p><a href="/File:GEOSS_Registries.png" class="image" title="GEOSS Registries"><img alt="GEOSS Registries" src="/w/images/thumb/3/36/GEOSS_Registries.png/400px-GEOSS_Registries.png" decoding="async" width="400" height="307" srcset="/w/images/thumb/3/36/GEOSS_Registries.png/600px-GEOSS_Registries.png 1.5x, /w/images/thumb/3/36/GEOSS_Registries.png/800px-GEOSS_Registries.png 2x" /></a> </p> <ul><li>Stores requirements by generalized user types that identify observables and their properties (e.g. values, quality, resolution, frequency, units of measure) with respect to a domain of application</li> <li>Matching of requirements to service offers can be made in the future as a common vocabulary of observables is developed for GEOSS to: <ul><li>Identify coverage and popularity of observations, and</li> <li>Identify gaps in coverage of observations</li></ul></li></ul> <h3><span class="mw-headline" id="URR_Administrative">URR Administrative</span></h3> <ul><li>UIC recommends the inclusion of a requirements registry for earth observations to be integrated with the existing</li></ul> <p>services and standards. Requirements available from several members. </p> <ul><li><ul><li>Joint effort and discussion document with UIC is needed to clarify the needs, interaction, governance, and approach of a solution; Could this be achieved through a new Task?</li></ul></li> <li>GEOSS Earth Observation taxonomy or ontology suggested to facilitate association of requirements, services, and applications <ul><li>Identify requirements for “observables” ontology drawn from the existing EO communities in order to associate applications, needs, and available services</li></ul></li></ul> <hr /> <p>Tie in with ADC GCI: </p> <ul><li>Need to formalize UIC commitment for the operation and interaction with the registry – significant governance issue</li> <li>Web-form upload by privileged individuals anticipated</li> <li>Batch upload from existing requirements systems also anticipated</li> <li><b>Architectural tie-points exist between the “observations” (observable parameters) and the Services and Standards Registries</b></li></ul> <p><b></b> </p> <ul><li>Continued web services and database support to be offered by this Task to UIC during IOC</li></ul> <h3><span id="User_Requirements_Registry_Features_(Gary_Foley)"></span><span class="mw-headline" id="User_Requirements_Registry_Features_.28Gary_Foley.29">User Requirements Registry Features (Gary Foley)</span></h3> <ul><li>A “user engagement” entry point for the Novice Users coming to the GEO Home Page</li> <li>Initially populated from the US-09-01a reports</li> <li>Shares info on registered types, applications and requirements; allows users to comment</li> <li>Allows users to register their type, applications, and requirements</li> <li>A standard vocabulary/ontology for use in registration</li> <li>Provides requirements for “Gap Analysis”</li></ul> <h3><span id="User_Classes_for_Air_Quality_(Gary_Foley)"></span><span class="mw-headline" id="User_Classes_for_Air_Quality_.28Gary_Foley.29">User Classes for Air Quality (Gary Foley)</span></h3> <ul><li>Public Information Delivery</li> <li>Public Emergency & Health Officials</li> <li>Operational Modeling Forecasting</li> <li>Local & Regional Environmental managers</li> <li>Earth Observation Community</li></ul> <h2><span class="mw-headline" id="Activities_of_Each_User_Class">Activities of Each User Class</span></h2> <h2><span class="mw-headline" id="HP_Plag:">HP Plag:</span></h2> <ul><li>SBA-Specific Work Flow Scenarios and Test Cases</li></ul> <p>Three Test Cases: </p> <ul><li>Air Quality and Health: Results of the SBA analysis (sub-SBA Health)</li> <li>Geohazards: 2008 Review of Requirements (sub-SBA Disaster)</li> <li>GGOS 2020: Cross-cutting (at least seven SBAs)</li></ul> <h2><span class="mw-headline" id="Activities">Activities</span></h2> <ul><li>Participate in monthly calls of the Analysts <ul><li>Two face-to-face meetings of the Analysts</li> <li>Assist with developing concepts and approaches for cross-cutting analyses of the observational priorities and other important information from the 2009 US-09-01a primary reports.</li></ul></li> <li>Conduct further analyses of the area of the Health SBA that would further this cross-cutting effort.</li> <li>Engage the AG <ul><li>Replace members, as needed.</li> <li>Ensure that the AG members have access to the primary and secondary products, as appropriate.</li></ul></li> <li>Database of keywords for the Health SBA area using the 2009 US-09-01a report as the source material for the keywords.</li> <li>Populating the User Requirements Registry (URR) and databases with the appropriate information from the primary and secondary products of the 2009 work.</li> <li>Conduct an international GEO workshop in the aeroallergens area of the Health SBA jointly with other sponsors to <ul><li>engage users</li> <li>engage observation providers</li> <li>support new Communities of Practice</li> <li>present the results of this task</li> <li>further populate the URR</li> <li>share new GEO-relevant scientific and technical results</li> <li>identify voluntary efforts to initiate additional activities, etc.</li></ul></li></ul>

@@ Line 1: / Line 1: @@
 <noinclude>{{GEO User Requirements for Air QualityBacklinks}}</noinclude>
+Erin: Make Dynamic List for GEO_URR Tags
+See also [[GEOSS User Requirements Registry]]
+<html><iframe src="http://webapps.datafed.net/AQ_needs.uFIND?table=http://capita.wustl.edu/capita/urr/AQLinks.xls" height="800" width="600"  ></html>
+== User Requirements Registry (D. Niebert, 2009)==
+[[Image:GEOSS Registries.png| GEOSS Registries|400px]]
+* Stores requirements by generalized user types that identify observables and their properties (e.g. values, quality, resolution, frequency, units of measure) with respect to a domain of application
+* Matching of requirements to service offers can be made in the future as a common vocabulary of observables is developed for GEOSS to:
+** Identify coverage and popularity of observations, and
+** Identify gaps in coverage of observations
+=== URR Administrative===
+* UIC recommends the inclusion of a requirements registry for earth observations to be integrated with the existing
+services and standards. Requirements available from several members.
+** Joint effort and discussion document with UIC is needed to clarify the needs, interaction, governance, and approach of a solution; Could this be achieved through a new Task?
+* GEOSS Earth Observation taxonomy or ontology suggested to facilitate association of requirements, services, and applications
+** Identify requirements for “observables” ontology drawn from the existing EO communities in order to associate applications, needs, and available services
+----
+Tie in with ADC GCI:
+* Need to formalize UIC commitment for the operation and interaction with the registry – significant governance issue
+* Web-form upload by privileged individuals anticipated
+* Batch upload from existing requirements systems also anticipated
+* '''Architectural tie-points exist between the “observations” (observable parameters) and the Services and Standards Registries
+'''
+* Continued web services and database support to be offered by this Task to UIC during IOC
+=== User Requirements Registry Features (Gary Foley)===
+* A “user engagement” entry point for the Novice Users coming to the GEO Home Page
+* Initially populated from the US-09-01a reports
+* Shares info on registered types, applications and requirements; allows users to comment
+* Allows users to register their type, applications, and requirements
+* A standard vocabulary/ontology for use in registration
+* Provides requirements for “Gap Analysis”
+=== User Classes for Air Quality (Gary Foley)===
+* Public Information Delivery
+* Public Emergency & Health Officials
+* Operational Modeling Forecasting
+* Local & Regional Environmental managers
+* Earth Observation Community
+== Activities of Each User Class ==
+== HP Plag: ==
+* SBA-Specific Work Flow Scenarios and Test Cases
+Three Test Cases:
+* Air Quality and Health: Results of the SBA analysis (sub-SBA Health)
+* Geohazards: 2008 Review of Requirements (sub-SBA Disaster)
+* GGOS 2020: Cross-cutting (at least seven SBAs)
+== Activities ==
+* Participate in monthly calls of the Analysts
+** Two face-to-face meetings of the Analysts
+** Assist with developing concepts and approaches for cross-cutting analyses of the observational priorities and other important information from the 2009 US-09-01a primary reports.
+* Conduct further analyses of the area of the Health SBA that would further this cross-cutting effort.
+* Engage the AG
+** Replace members, as needed.
+** Ensure that the AG members have access to the primary and secondary products, as appropriate.
+* Database of keywords for the Health SBA area using the 2009 US-09-01a report as the source material for the keywords.
+* Populating the User Requirements  Registry (URR) and databases with the appropriate information from the primary and secondary products of the 2009 work.
+* Conduct an international GEO workshop in the aeroallergens area of the Health SBA jointly with other sponsors to
+** engage users
+** engage observation providers
+** support new Communities of Practice
+** present the results of this task
+** further populate the URR
+** share new GEO-relevant scientific and technical results
+** identify voluntary efforts to initiate additional activities, etc.
+[[Category:GEO_URR]]