Enhancing GEO Architecture for Better User Experience

1. Architecture Priorities

2. Why do stakeholders perceive that the architecture does not meet needs? • Users are not seeing what they expect • The interaction or UI is cumbersome and requires human intervention • Scientists already find what they need in their communities • No perceived GEO-added value • Insufficient outreach on successful solutions

3. What emerging architectural elements should be introduced? • Focus on data-side services to be deployed as the primary value-add of GEO • Support for an organic vocabulary for observable properties (ontologies) • Supporting web service integration and chaining (work flows, mashups)

4. Moving R&D into later operations • Ontology support and brokered search is demonstrated by EuroGEOSS and should be evaluated for transition to GCI operations. Select among datasets from EuroGEOSS. • FedEO and GENESI-DR “demonstrator” search of imagery inventories could be enabled and integrated into GeoPortal search using OpenSearch-geo. Subset of data sets to be identified from Observational Priorities. [ESA]

5. GCI enhancements • Single search capabilities against Clearinghouse from GEOPortal • Flag and deploy of categories/tags (location, time, publisher, Data-CORE, “no cost,” data quality, etc.) in order to group/manage results • Render selected services found through Clearinghouse (i.e. mapping WMS, GeoRSS) • Investigate and improve ranking of results • Integrate User Requirements Registry with GCI

6. CSR/Clearinghouse improvements • Simplify registration process and “resource types” • Allow association of multiple standards with any resource • Support ISO metadata as core model • Investigate consolidation of CSR and CH as a single search engine • Expose all CH metadata as HTML and sitemap.xml for commercial search engines (CSE)

7. Architecture Implementation Pilot (AIP-4) • AIP-4 will focus on promoting high-priority data sources to be exposed as online web services to enable maximum re-use, show rapid progress • Start with Observation Priorities from UIC, Data-CORE nominations, and other key data sets (i.e. ECV, ETV) • Support a taxonomy to ‘flag’ these resources for search/presentation in GeoPortal and CH • Enable end-user visualization and data access through the GEO Web Portal • Promote extensive outreach on the success of projects, engage selected user communities, UIC, CBC, incidental to the testing and deployment process • Frame outcomes and recommendations to ADC/GEO from AIP-3 – reformulate the summary and resolutions

8. Metadata • Identify and build consensus on “Minimal GEOSS Metadata” Profile of ISO metadata and Profiles recognized and mapped for use in GEOSS • Address GEO-specific fields/tags to be managed, to be subject of next CC telecon – need work telecon first to also address among GCI Providers and invited experts: • Data-CORE flags and links and • Data quality and links to references • Support data semantics – ontology for data containing priority observation parameters stored in ISO or as supplemental structured metadata (as RDF/OWL/SKOS?)

9. Action: Facilitate deployment • Use as reference the common set of observational parameters – priority observations - from US-09-01 Table 13 and Data-CORE list [AIP Team and GEOSec SBA experts (George) – March, initial] Identify accessible data sets supporting the observational parameters, working with subject experts, to enable online services (review Data-CORE survey) to showcase priority data access. Capture status of accessibility [(Rob) SME/Secretariat experts, data providers, AIP, GCI operators - April] • For gaps (parameters in data sets that are not internet accessible), contact key providers via the Secretariat and ADC to add extra service adapters to priority data sources [(Rob) Secretariat – May] • Demonstrate client access to GENESI-DR, EuroGEOSS, AIP-4 services for users [(Mirko, Jay, AIP Team) ESA – May/June] • Enable online services to showcase priority data access by 2011 Plenary with full data access through the GEO Portal - “Services on the data” Include Data-CORE and quality declarations, proper metadata, support standard data access service interfaces [(Mirko, George) data providers, AIP, GCI operators – September] • Demonstrate integrated access to critical GEO resources for the Plenary [(Gary Foley) October] • Integration/use of the priority observation data – consult with UIC Communities of Practice for demo. Measure usage/access, usability assessment [UIC (Gary Foley) - November]

10. New Activity Proposal • Need a support team that can assist in registering new data sources and in deploying quality Web services • Intervention, proactive: target priority data providers • Support capacity building and showcases • Work with priority communities and data resources to prove value-add • Engage commitment at the management level • Need sponsors/participants

11. Activity: Operations and Enhancement • Process has been proposed for Ops and Enhancement Board or Team to include all GCI providers and key stakeholders to accept and process bug fixes and enhancements • Supports formal management of enhancements and fixes to all of the GCI system components • Have held multiple GCI Providers telecons to address urgent issues – need a formal recognition and host for this before the next work cycle

12. Task: GEOSS Architecture • Replacement of AR-09-01a • Maintains and updates the latest requirements and designs of the GEOSS Architecture to respond to requirements on a periodic cycle • Supports strategic and tactical approach, documentation, and outreach

13. Task: GEOSS Development • Update on AR-09-01b • Continues the AIP R&D process provides feedback and recommendations for operations

14. Task: Ontologies • Update on AR-09-01d with EuroGEOSS • Maintain registry of ontologies from communities • Building ontology of observation parameters with all data offerings and user requirements • Facilitates brokered “smart” search and data integration • Includes operational and research scope – clarify interactions