GEOSS Community Portal Recommendations

Report to the IIB

Topics

• Presentation to the WPS– Description of the activity– Outreach to full GEO community– Encourage participation/collaboration

• Discussion topics for the IIB– General direction of the activity– Issues in need of resolution– Challenges in producing/maintaining the

report

GEOSS Community Portal Recommendations

Team Report

Outline

• Motivation– Why do we need this paper?

• Approach– How are we developing it?

• Team– Who is working on it?

• Document Overview– What will be produced?

• Status and Plans– When will it be completed?

5

GEOSS Common Infrastructure

• The GCI supports access to all registered GEOSS resources

• The GEOSS Portal interfaces with the Discovery/Access Broker (DAB) to discover, search and access resources in the GCI registries and those within large, federated EO catalogues.

• The GEOSS Portal allows filtering on science and application disciplines of the Societal Benefit Areas.

Rationale for Community Portals

• As good and necessary as the GEOSS Portal is, communities still wish to develop their own interface to relevant data and services– Provides visibility to their particular program– Supports integration of EO and non-EO data– Enables integration of specialized community services

• Ideally Community Portals will utilize GCI for discovery and access of EO (GEOSS) data and services– GCI can enable CPs to present a community-specific view of GEOSS

resources

• Communities will need assistance– GCI documentation, recommendations, best practices, tutorials, etc.

Community Portal Role in GEOSS

CommunityPortal

Community

Catalogue

Community

Broker

CommunityInfrastructure

Community Data, Services and Applications

Link from GEOSS Portal

Community View ofGEOSS Resources

Register Community Resources as Appropriate

Enables Integration ofGEOSS and non-GEOSS

Resources

Community Portal Paper Activity

• Purpose – assist developers of Community Portals– Demonstrate benefits of utilizing GCI– Instruct on its use– Share experience of previous efforts (e.g. AIPs)

• Team – voluntary representatives from GCI component developers and interested communities– Communities at varying stages of portal development and with

different levels of experience with GEOSS/GCI– Good representation from AIP participants

• Goal – maximize benefits of GCI and promote community contributions to system of systems

Team Members

Ken McDonald/NOAA-STC Martin Yapur/NOAA

George Percivall/OGC David Arctur/OGC

Yubao Qiu/GEO Sec Jan Rene Larsen/AMAP

Osamu Ochiai/GEO-Sec Oliver Clements/PML

Espen Volden/GEO-Sec Bart de Lathouwer/OGC

Stefano Nativi/CNR Arne-Jørgen Berre/SINTEF

Mirko Albani/ESA Lionel Menard/MINES-ParisTech

Doug Nebert/USGS Laurence Fleury/OBS-MIP

Martin Hogeweg/ESRI Mick Wilson/UNEP

Steve Browdy/IEEE/OMS Tech Guido Colangeli/ESA

Greg Giuliani/UNEP Gary Geller/JPL-GEO BON

Glenn Rutledge/NOAA-NCDC

Dual Purpose Document• Marketing

– Introductory statement of the purpose and scope of the paper– Good understanding of the objectives and needs of the various

communities– Clear presentation of the GCI capabilities and interfaces

• Enabling– Complete set of instructions, tutorials, recommendations, best

practices and examples– Recommendations should include rationale– Document should accommodate different levels of

integration/interaction between GCI and community systems (i.e. different use cases)

Progress to Date• Initial telecons focused on information sharing

– Energy Portal – Lionel Menard– Sustaining Arctic Observing Networks – Jan Rene Larsen– GEOSS Discovery/Access Broker – Stefano Nativi– GEOSS Portal Overview/Demo – Guido Colangeli– Portals of the Water SBA – David Arctur– Portals of Citizens Observatories – Arne J. Berre– EnviroGRIDS – Greg Giuliani

• Community Portal use cases developed• Rough draft of paper near completion

– Describes purpose, scope, GCI overview and use cases– Provides structure for capturing recommendations

Delivery of Document

• Initial delivery of recommendations will be a published document

• Ongoing updates are envisioned– Experience of portal development efforts– Evolution of GCI components– New or revised use cases

• Options for delivery of updates being discussed– Regularly scheduled document releases– Website with ongoing updates

IIB DiscussionGeneral Direction of the Paper

• Purpose– Both encourage and enable use of GEOSS/GCI?

• Use Cases/Definitions– Community Portal / Community GEOSS Portal / Applications

• Scope– Plan to focus on Community GEOSS Portals but address other use cases

– Access to both GEOSS and non-GEOSS resources (e.g. EO and non-EO data)

• Rationale– Community use of GEOSS promotes Community ownership and

contributions…

– …encourages use of GEOSS standards and best practices…

– …facilitates greater integration in the future.

IIB DiscussionIssues

• GCI evolution– Multiple interfaces to DAB and Clearinghouse– Changes to registration procedure– Need resolution before making recommendations

• Best source of information– Related to evolution– Architecture Design Document (ADD) good source but out of date– Recent UML diagram still being discussed

• Support– Are GCI component developers ready to assist Community Portal

developers?

IIB DiscussionChallenges

• Completing the draft document– Purpose, scope, discussion of community needs, use cases/definitions in draft

form– Multiple examples from AIP and other efforts can be referenced (e.g. Energy

Portal, Water Portals, EnviroGRIDS)– Still need good GCI description as discussed in issues– Will need tutorials on interfacing to DAB (and/or other components) and

registration– Then we can propose and discuss recommendations

• Timing of document release– Continuing to circulate releases to writing team– Propose delaying more general release until GCI and registration issues

resolved– Need authoring help from overly-committed experts