Best Practices Wiki Ruth Duerr NSIDC, IEEE Jay Pearlman, IEEE Siri Jodha Singh Khalsa, IEEE Report to GEO Committees February 2008.

Slides:



Advertisements
Similar presentations
GEOSS ADC Architecture Workshop Break-out summaries: Initial Operating Capability (IOC) Doug Nebert U.S. Geological Survey February 5,
Advertisements

GEOSS ADC Architecture Workshop: Portals Ingo Simonis iGSI
PAC 2008 Activities Joan Carletta, PAC Chair 15 November 2008 New Brunswick, NJ, USA EAB Public Awareness Committee (PAC)
© GEO Secretariat Agenda Item 3. GEO UPDATE. © GEO Secretariat Membership 67 members and 43 Participating Organisations – New Members:Latvia, Moldova,
GEOSS Game Contest 3rd GEO Capacity Building Committee Meeting Tenerife – 2 February 2007.
AR – Issues for Attention Tactical and Strategic Guidance documents – what is the agreed approval/ publication process? –Strategic Guidance will.
1 Guy Duchossois, Work Plan Manager Report on 2006 Work Plan.
Report of the Architecture and Data Committee (ADC) for the C4 Meeting Ivan B. DeLoatch, ADC Co-chair June 2008.
GEO-5 in Ottawa 1 29 November 2004 Draft GEOSS 10-Year Implementation Plan and Status Report on Reference Document Ivan B. DeLoatch, Toshio Koike, Robert.
SIF Status to ADC Co-Chairs
Core Task Status, AR Doug Nebert September 21, 2008.
Standards and Interoperability Forum: Status, Issues & Plans GEO Architecture and Data Committee Kyoto, Japan 9 February 2009 Siri-Jodha Singh Khalsa.
Call for Proposals: Earth Observations in Decision Support Joint Effort of GEO Capacity Building Committee and User Interface Committee March 2009.
Managing Interoperability for GEOSS - A Report from the SIF S.J. Khalsa, D. Actur, S. Nativi, S. Browdy, P. Eglitis.
ADC Meeting Summary Geneva, May 2008 Alessandro Annoni, JRC Jay Pearlman, IEEE Report to Capacity Building Committee May 22, 2008.
GEOSS Common Infrastructure (GCI)
Slide # 1 Report to ADC AR Status Doug Nebert, POC U.S. Geological Survey.
Integrated Ocean Observing System (IOOS) Data Management and Communication (DMAC) Standards Process Julie Bosch NOAA National Coastal Data Development.
© GEO Secretariat The Group on Earth Observations – Status and Post 2015 Osamu Ochiai GEO Secretariat 41 st CGMS Tsukuba, Japan 8-12 July 2013.
Architecture Decision Group Group Organization & Processes April 7, 2015 | Tuesday.
Text #ICANN51 GNSO PDP Improvements Status Update.
Process for Publishing Best Practices and Lessons Learned Martin Yapur, NOAA WGISS – 29 May 17, 2010 Bonn, Germany.
Architecture and Data Management Strategy (Action Plan) Ivan 1 DeLoatch, USGS, ADC Co-chair Alessandro Annoni, EC, ADC Co-chair Jay Pearlman, IEEE, ADC.
Open Library Environment Designing technology for the way libraries really work November 19, 2008 ~ ASERL, Atlanta Lynne O’Brien Director, Academic Technology.
GEOSS Architecture Describes how components fit together for providing data and information that will be better …than the individual components or systems.
Data integration and dissemination in the MARsite project John Douglas (WP10 leader)
GEOSS Common Infrastructure: A practical tour Doug Nebert U.S. Geological Survey September 2008.
Report of the IOC Task Force on the GEOSS Common Infrastructure (GCI) Ivan DeLoatch, U.S. Geological Survey Alan Edwards, European Commission Co-chairs.
ADC Meeting ICEO Standards Working Group Steven F. Browdy, Co-Chair ADC Workshop Washington, D.C. September, 2007.
Best Practices Wiki Ruth Duerr NSIDC, IEEE Jay Pearlman, IEEE Siri Jodha Singh Khalsa, IEEE Report to GEO Committees February 2008.
Best Practices Wiki Ruth Duerr NSIDC, IEEE Jay Pearlman, IEEE Siri Jodha Singh Khalsa, IEEE Report to ADC Committee May 21, 2008.
Best Practices Wiki Ruth Duerr NSIDC, IEEE Report to GEO Committees September, 2008.
© GEO Secretariat 5.2 Monitoring and Evaluation John Adamec Co-Chair, M&E Working Group GEO-XI Plenary November 2014 Geneva, Switzerland.
Update on Current EGNRET Projects APEC EGNRET 23 Meeting Christchurch, New Zealand ~ November 10-12, 2004 Jean Ku National Renewable Energy Lab, USA Cary.
The Caribbean Knowledge Management Portal Knowledge Management for the Caribbean Information Society.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
1 Group on Earth Observations WORLD METEOROLOGICAL ORGANIZATION Weather – Climate - Water Dr Donald Hinsman, WMO Secretariat Focal Point for GEO.
GEO Architecture and Data Committee Task AR Architecture Implementation Pilot George Percivall Open Geospatial Consortium GEO Task AR Point.
GEO Work Plan Symposium 2012 ID-03: Science and Technology in GEOSS ID-03-C1: Engaging the Science and Technology (S&T) Community in GEOSS Implementation.
SIF Status to ADC Co-Chairs Siri Jodha S. Khalsa Steve Browdy.
GEOSS Common Infrastructure Internal Structure and Standards Steven F. Browdy (IEEE)
WGISS-39, Tsukuba, Japan, May 11-15, 2015 GEO Community Portals Ken McDonald/NOAA CWIC Session, WGISS–39 May 13, 2015.
© GEO Secretariat Work Plan Guidance document 2 nd Capacity Building Committee Meeting, Brussels September 2006.
Best Practices Wiki Ruth Duerr NSIDC, IEEE Jay Pearlman, IEEE Siri Jodha Singh Khalsa, IEEE Report to GEO Committees February 2008.
GEOSS Interoperability Workshop November 12-13, Introduction to the SIF Steven F. Browdy, IEEE
Slide # 1 Report to the GEO ADC on the Standards and Interoperability Forum 12 Sept 2007 National Academy of Sciences Washington, D.C. IEEE Committee on.
GEOSS Common Infrastructure (GCI) & GCI-Coordination Team (GCI-CT) Ivan Petiteville, GCI-CT Co-chair GEO Architecture & Data Committee meeting Campos do.
Company Confidential Registration Management Committee RMC Auditor Workshop Charleston, SC July 2015 The OASIS Feedback Process Empowering Communication.
GEO Standards and Interoperability Forum SIF First Organizational Meeting 27 July 2007 Barcelona, Spain.
Robert S. Chen Co-chair/Data Sharing Task Force Geneva, Switzerland 1-3 February 2011 Implementation of the GEOSS Data Sharing Principles.
Task XX-0X Task ID-01 GEO Work Plan Symposium April 2014 Task ID-01 “ Advancing GEOSS Data Sharing Principles” Experiences related to data sharing.
Architecture Task AR Status Presented to the July Meeting of the GEO and Architecture and Data Committee Dr. Thomas C. Adang AR Point.
The Process for Achieving Interoperability in GEOSS AGU Fall Meeting IN43C-08.
Core Task Status, AR Doug Nebert September 22, 2008.
GEOSS Common Infrastructure Initial Operating Capability Directions and Discussion Presented to GEO ADC Geneva May
GEOSS Common Infrastructure Access to Priority Earth Observations Data “ Sprint to Plenary” Group on Earth Observations Eighth Plenary Session - GEO-VIII.
ISWG / SIF / GEOSS OOSSIW - November, 2008 GEOSS “Interoperability” Steven F. Browdy (ISWG, SIF, SCC)
ISWG / SIF / GEOSS OOS - August, 2008 GEOSS Interoperability Steven F. Browdy (ISWG, SIF, SCC)
GEOSS Common Infrastructure (GCI) The GEOSS Common Infrastructure allows Earth Observations users to search, access and use the data, information, tools.
Capacity Building in: GEO Strategic Plan 2016 – 2025 and Work Programme 2016 Andiswa Mlisa GEO Secretariat Workshop on Capacity Building and Developing.
Introduction to the GEOSS Registries: Components, Services, and Standards Doug Nebert U.S. Federal Geographic Data Committee June 2007.
What We Need to Launch Community Buy-in Web Page in Place
Paul Eglitis [IEEE] and Siri Jodha S. Khalsa [IEEE]
Introduction to the GEOSS Component and Services Registry
AR Doug Nebert, POC-elect GEO ADC Co-Chairs Meeting,
The Architecture of GEOSS Dr
The Standards and Interoperability Forum
Core Task Status, AR Doug Nebert September 22, 2008.
Status Report on SIF to GEO ADC
Air Quality Data Systems and the GEOSS Architecture
Presentation transcript:

Best Practices Wiki Ruth Duerr NSIDC, IEEE Jay Pearlman, IEEE Siri Jodha Singh Khalsa, IEEE Report to GEO Committees February 2008

What is a best practice? Best practices can be in outreach and capacity building, observation techniques or models and analysis They can be very simple or complex They can be local, regional or global They can be determined by peer acceptance

Best Practices within the Architecture GEO Portal Standards and Interoperability Forum GEOSS Contributor Users GEOSS Clearinghouse GEOSS Standards and Interoperability Registry Standards Special Arrangements Components Registry Services Registry GEOSS Component and Service Registries GEOSS Components & Services Community Catalogs Best Practices Wiki

Wiki – what is that? Wiki software is a type of collaborative software that typically allows web pages to be created and edited by all participants using a common web browser.

How does a “Wiki” work? Wiki software is collaborative software that allows web pages to be created and edited. Wiki software is collaborative software that allows web pages to be created and edited using a common web browser. Wiki software is collaborative software that allows web pages to be created and edited by all participants using a common web browser. Wiki software is a type of collaborative software that typically allows web pages to be created and edited by all participants using a common web browser.

Why use a Wiki? Provides an open forum for converging on best practice recommendations and reviews Reaches out to a broad community Flexible structure can be easily adapted using lessons learned Can be a clear contribution of GEOSS to the global community

Best Practices Wiki Objective: facilitate population of an open access repository of accepted best practices for GEOSS WIKI.IEEE-EARTH.ORG

Best Practices Wiki

BP Wiki Concept of Operations Individual or organization proposes a practice for consideration as a “best” practice by submitting an entry in the wiki. Submitted practices undergo an open peer review process. –Comments in the wiki are publicly accessible, facilitating a moderated community dialog. Facilitators work with SMEs to encourage dialog and submission of comments Facilitators also assure that malicious insertions are eliminated. –Original contributors should also monitor activities

Facilitator Activities review newly submitted practices for applicability to their subject areas and to address any erroneous or malicious entries periodically review and respond to comments on practices in their area that are in the review process To solicit comments on proposed practices from their communities solicit proposed practices from their communities if needed annotate conflicts between practices in the wiki in the hopes of eliciting further review and comments leading to resolution of the conflict To keep their communities informed about the status of the practices that have been proposed in their area correspond with submitters to keep them informed of the status of their submittal (this may be automated) recommend approval, disapproval, or modification of a proposed practice to the editorial team at the end of the review period, and changes in status periodically thereafter collaborate with other members of the “editorial” team and participate in “team” activities including periodic telecoms, etc.

Development Plan First pilot –Initial checkout with option selected – 3 mo. –Assessment (clean out any test entries) & rework – 1 mo. Second pilot –Checkout with upgrades and updated processes – 3 mo. –Assessment & rework – 1 mo. Final test period – 1 mo. Operational system configuration announced to all of GEO - 1 Nov 08

First Pilot Phase The first pilot is to test the usability and usefulness of the Wiki, as well as to develop and test the facilitation processes. Two options: –Focus the initial alpha pilot phase on several areas offered and supported by communities of practice or science/technology teams –Open the alpha pilot phase to all inputs with the possibility that there would be a broad, but thin contribution and dialogue.

ISSUES (I) How to handle “best” practices that have already been accepted by other international organizations? –For example, after a CODATA committee on data management best practices completes its work in Nov. 2008, upon approved by the full committee these practices will be submitted as best practices for GEOSS. How would CODATA address the responses? Should submitters be expected to place the full text of their practice on a Wiki page or may they supply a full description of the practice as attached files? Some of the considerations are: –Allowing attachments greatly simplifies the submission process thereby increasing the likelihood of submissions at the likely expense to users that are searching for practices on a particular topic.

ISSUES (II) The scalability of the existing Wiki needs to be assessed –planned at the end of the second pilot How easy it will be to maintain a stable commitment from members of the facilitation team? Will a reward structure be necessary? What do we do if activity on the Wiki is low and entries are few? It may be necessary to solicit entries.

Best Practices Wiki - Summary Wiki is on-line at Expert volunteers in the pilot subjects are being solicited Entries are welcome in the pilot phase subject areas Comments on the process should be provided to Ruth Duerr at Your participation is important. Exposure of the Wiki through Members and Organizations and the GEO Secretariat is critical to BP utility