Welcome!

DAY 1

Facility Overview

• Entering and Exiting– Rear entrance is closest to the auditorium– Perimeter doors are not secure– Do not exit through the auditorium rear

emergency doors• Restrooms

– Located near the 2nd floor front entrance, left of the double doors

• In Case of Emergency– Please exist through the rear doors of the

auditorium and proceed down the rear stairwell

Facility Overview

• Security– Be sure to sign in at the beginning of each day– Entrance into a Raytheon work area will require a Raytheon escort

• Parking– No visitor parking registration is needed– Please park in unmarked spots to avoid being towed

Workshop Overview

• Food & Drink– Food and Drink are allowed in the auditorium.

• Breaks & Lunches– Periodic breaks will be provided during the workshop– Lunch will be brought in for those who pre-registered

• Wireless Access– Access to the RaytheonVAG wireless network requires a user name and

password• Pre-registered attendees will have an account provided

• Teleconferencing– The ECHO teleconference # (877.973.2179 Passcode 770291) will be used– A WebEx live session will also be available. Details provided separately.

• Discussions– Questions should be asked as the presentations proceed.– Some discussions may be tabled for the designated Q&A periods

Agenda Overview

• Day One– 9:00am ~ 4:30pm– Focus entirely on Reverb discussion topics including:

• Reverb Showcase• Reverb Functional Overview• Reverb Automation• Reverb Technical Topics• WIST2REVERB Transition• Reverb Future Changes

• Day Two– 9:00am ~ 12:00pm– Focus shifted to ECHO engineering topics including:

• Upcoming ECHO Changes• Upcoming Operational Activities

ECHO Organization

Tim Ortiz (Program Manager)

Lisa Pourkhomami

(Dev Lead)

Bob Hartranft (DBA Lead)

Marcus White* (SA Lead)

Ayanna Dennis* (OPS Lead)

Art Cohen (Task 3 Lead)

(Release Manager)

Dan Pilone (Tech Lead)

Matt Cechini (Sys Engineer)

ECHO TEAM INTRODUCTIONS

Reverb MVP Award

• Honorable Mentions– Kelly Lemig – 42 NCRs– Jon Pals – 17 NCRs– Dawn Siemonsma – 15 NCRs

• Sample Bug Report

PETER GIBBONSMVP

OPERATIONS STATUS

ECHO Partner Status

• Current Holdings – Collections 3,227– Granules94 million – Browse 35 million (internal) / 22 million (external)

• Data Partners– Operational: 13

• ASF, GHRC, GSFC, LAADS, LARC (ECS), LARC (ANGe), LPDAAC, NSIDC (ECS), NSIDC (V0), PODAAC, ORNL, SEDAC, USGS_EROS

– Test: 1 • CDDIS

• Client Partners– Operational 5

• WIST, ESA, MTMGW, GMU, ECHO-ESIP– In evaluation or test 6

• MIRADOR (OpenSearch), YOTC (OpenSearch), Reverb, SCS3, Mercury, CWIC

– Development/Design 3• AVAPC, J-Earth, PO.DAAC

ECHO Client Usage (1 of 2)

02/06 - 02/12

02/13 - 02/19

02/20 - 02/26

02/27 - 03/05

03/06 - 03/12

03/13 - 03/19

03/20 - 03/26

03/27 - 04/02

04/03 - 04/09

04/10 - 04/16

04/17 - 04/23

04/24 - 04/30

05/01 - 05/07

0

2000

4000

6000

8000

10000

12000

14000

WIST & Reverb Granule Queries

ECHO Client Usage (2 of 2)

02/06 -

02/12

02/13 -

02/19

02/20 -

02/26

02/27 -

03/05

03/06 -

03/12

03/13 -

03/19

03/20 -

03/26

03/27 -

04/02

04/03 -

04/09

04/10 -

04/16

04/17 -

04/23

04/24 -

04/30

0500

1000150020002500

Non-WIST Granule Queries

Query Performance

02/06 - 02/12

02/13 - 02/19

02/20 - 02/26

02/27 - 03/05

03/06 - 03/12

03/13 - 03/19

03/20 - 03/26

03/27 - 04/02

04/03 - 04/09

04/10 - 04/16

04/17 - 04/23

04/24 - 04/30

05/01 - 05/070

102030405060708090

100 Average Query PerformanceSe

cond

s

Order Metrics (1 of 2)

*All orders submitted by WIST.

0

200

400

600

800

1000

1200

1400

1600

02/13 - 02/1

9

02/20 - 02/26

02/27 - 03/05

03/06 - 03/12

03/13 - 03/1

9

03/20 - 03/26

03/27 - 0

4/02

04/03 - 04/09

04/10 - 0

4/16

04/17 - 0

4/23

04/24 - 04/30

05/01 - 0

5/070

500

1000

1500

2000

2500

Axis Title

Order Metrics (2 of 2)

03/13 - 03/19

03/20 - 03/26

03/27 - 04/02

04/03 - 04/09

04/10 - 04/16

04/17 - 04/23

04/24 - 04/30

0

200

400

600

800

1000

1200

1400

1600

1800

2000WIST vs. Reverb Orders & Downloads

# O

rder

s or D

ownl

oads

Ingest Activity

11/21

- 11/2

7

11/28

- 12/0

4

12/05

- 12/1

1

12/12

- 12/1

8

12/19

- 12/2

5

12/26

- 01/0

1

01/02

- 01/0

8

01/09

- 01/1

5

01/16

- 01/2

2

01/23

- 01/2

9

01/30

- 02/0

5

02/06

- 02/1

20

200,000

400,000

600,000

800,000

1,000,000

1,200,000

1,400,000

1,600,000

02/06

- 02/1

2

02/13

- 02/1

9

02/20

- 02/2

6

02/27

- 03/0

5

03/06

- 03/1

2

03/13

- 03/1

9

03/20

- 03/2

6

03/27

- 04/0

2

04/03

- 04/0

9

04/10

- 04/1

6

04/17

- 04/2

3

04/24

- 04/3

0

05/01

- 05/0

70

200,000

400,000

600,000

800,000

1,000,000

1,200,000

1,400,000

1,600,000

1,800,000

2,000,000

< .25% Rejections

ECHO Availability

Feb-

09

Mar-

09

Apr-0

9

May-

09

Jun-

09

Jul-0

9

Aug-

09

Sep-

09

Oct-0

9

Nov-

09

Dec-

09

Jan-

10

Feb-

10

Mar-

10

Apr-

10

May-

10

Jun-

10

Jul-1

0

Aug-

10

Sep-

10

Oct-1

0

Nov-

10

Dec-

10

Jan-

11

94.0%

95.0%

96.0%

97.0%

98.0%

99.0%

100.0%

0

2

4

6

8

10

12

14

16

18

% A

vaila

ble

Durin

g M

onth

Hour

s

*ECHO HA solution deployed in March 2009** % Availability does not include PM (Up to 4 hours / week) outages

*** Downtime (Hours) _does_ include PM outages

Apr-1

0

May-

10

Jun-

10

Jul-1

0

Aug-

10

Sep-

10

Oct-1

0

Nov-

10

Dec-

10

Jan-

11

Feb-

11

Mar-

11

Apr-

11

May-

11

99.50%

99.55%

99.60%

99.65%

99.70%

99.75%

99.80%

99.85%

99.90%

99.95%

100.00%

0

1

2

3

4

5

6

7

% A

vaila

ble

Durin

g M

onth

Hour

s

PROCESS OVERVIEW

ONE GOAL

BUILD THE RIGHT SOFTWARE

Original Approach

Testbed• Alpha Release every 2

weeks• Open to the public• Early feedback• 20% Dev Time Reserved

for feature request and prioritization

Partner Test (Beta)• Early beta – approx Feb

2011• Open to the public with

WIST announcement• Solicit public input on

Reverb prioritization

Operational• May 2011• Already have a base of users

from beta testing• Smooth (ideally non-existent)

transition from beta testing• Allow for continued

evolution of Reverb

Development Lessons Learned

• Deployment overhead still too high to sustain 2 week alpha pushes– Nuances of new technologies contributed to costly build

process• Feedback focused more on features not-yet

implemented vs. testable functionality• Needed preview release in Partner Test

sooner than later to test end-to-end ordering outside of Ops

• 20% rework was sometimes difficult to plan for, but was very useful to address feedback concerns

• “Top 5” requests were helpful, but under-utilized

Modified Approach

• Monthly alpha release pushes to Testbed• Point releases as needed to meet major

milestones or to address significant bugs• Delayed beta testing until more

functionality was implemented• Plan in 20% rework to each development

sprint for bug fixes & enhancements per feedback

• Continue to request “Top 5”, but start nailing down required bug fixes for major milestones early

BETA RELEASE CHANGED THE DYNAMIC

NCR Metrics

July Aug Sept Oct Nov Dec Jan Feb Mar Apr May0

5

10

15

20

25

30

35

40

45

Externally Submitted NCRs

Initial Reverb Testbed deployment

Beta release prep-telecon

Beta-release

REVERB IS THE PLATFORM FOR FUTURE ECHO CLIENT INNOVATION

Moving Reverb Forward

• Core Reverb functionality will become part of monthly sustaining activities

• Reverb will become Operational on May 16• Development will continue with monthly

Alpha pushes to Testbed• Reverb Beta will continue to exist and serve

as a prototype space for T2R4 and potential client technology efforts

• Operational Reverb will be updated as part of the normal Operational deployments

Specific functionality will be discussed later today

REVERB SHOWCASE

Dataset Discovery

• First class dataset discovery• Fast keyword filtering of datasets• Ability to add entire datasets to

cart to support dataset download and ordering

• Ability to applyservices directly todatasets

• Temporal and spatialfiltering of datasetswithout doing agranule search

Improved Form Rendering

• Fully styled form rendering• Support for native controls

including spatial selectionareas on maps withmultiple projects

• Inline error and helpinformation

• Smooth form expansionand collapsing to showor hide input areas

• Same rendering engine usedfor Orders and Service invocations

Bulk Download

• Support for bulk download of large number of items

• Supports multiple download options• Text file of URLs to

support wget and curl

• FTP batch download script

Services

• Added dynamic servicediscovery and invocation

• Services can be associated using tags

• Leverages familiar ECHO Forms for service UI presentation to the user

• Can be extended to supportwide variety of APIs (e.g.: GLASSubsetter, ESI)

• User input can be as simple as selecting an area of interest and desired dataset.

Maintainability

• Reverb is based on modern web standards– Ruby on Rails3, HTML(5), CSS, JavaScript

• Fully automated valids, ACLs, and keyword generation

• Follows well established ECHO Development best practices

• Extensive suite of automated tests

Minimized Ops/DAAC Interaction

• Minimized Ops/DAAC Coordination– Reverb reduces the number of items on which ECHO data partners need to

coordinate with the ECHO Operations team.– Reduced coordination simplifies Reverb maintenance.– Data partners can modify Reverb interactions through modifying metadata.

Reverb-Enabled Metadata Cleanup

• Resolved Metadata Inconsistencies & Errors – Missing Collection Temporal Metadata– Missing Collection Spatial Metadata– Incorrectly defined “MODIS Tile” 2D Coordinate System– Invalid NSIDC Descending Crossing Longitude– Archive Center Cleanup

• Identified Metadata Issues– Inconsistent Processing Level Usage– Invalid LARC_ASDC Granule Temporal Values– Conflicting “ASTER” Instrument & Sensor– Invalid OnlineResourceURL MimeTypes– OnlineResource vs OnlineAccessUrl– Non-specific browse file extensions

REVERB AUTOMATION

WIST Valids

• WIST– Valids configured to run once/hour for guest users.

• Metadata or guest user access changes lags according to valids frequency.• Valids runs as a stand alone process, not integrated with WIST.

– Valids processing runs on-demand when a user logs in.• There are no lagging issues having to do with metadata modifications.

– Information Gathered for Dynamic Presentation• Collections available to guest users• Science Keywords• Additional Attributes

– ECHO Operations Configured Information• Data Quality Summaries & Assignments• Radio Button Mappings• 2D Coordinate Systems• Additional Attribute Grouping

Reverb Valids

• Reverb– Valids processing configured to run once/hour for guest users.

• Metadata or guest user access changes will lag in Reverb interface.• The valids process is integrated with Reverb and runs as a core part of the app.

– Valids processing runs on-demand when a user logs in. (No Change)• Valids are refreshed every hour for the registered user.

– Information Gathered for Dynamic Presentation• Search Terms• Platforms & Instruments• Campaigns• Science Keywords• Processing Levels• 2D Coordinate Systems• Calendar Events• Provider Holdings (Granule Counts)• Services (Including Dataset Tags)

Calendar Events

• WIST– Calendar events managed by providers in WIST Interface.– Username/Password not synchronized with ECHO system.– Alerts/Info displayed in scrolling banner & on separate calendar page.

• Reverb– Calendar events managed by providers in PUMP & made available to all ECHO

client partners through SOAP & REST API, or end users via RSS. – All provider and system calendar events loaded from the ECHO system.

• NCR 11010933 tracking issue re: Reverb displaying non-active events– ALERT events displayed in “Availability” section & INFO events displayed in

“Notices” section.– HTML formatting available for improved readability.

• Data Partner Responsibilities– Management of ECHO calendar events belongs to Data Partners.– Continue to update WIST & Reverb to reflect accurate alerts & info events.– Remove non-active events when the end-date has passed.

Data Quality Summaries

• WIST– Configured by ECHO Ops team in cooperation w/ Data Partners.– Displayed when user adds a collection or granule to their cart.– If a registered user has accepted the DQS and the DQS changes, they will not

be presented with the new DQS.• Reverb

– Data quality summaries managed by providers in PUMP & made available to all ECHO client partners through SOAP & REST API.

– Displayed when a user searches for granules within a dataset.– Modified DQS are displayed to registered and guest users.– HTML formatting available for improved readability.

• Data Partner Responsibilities– Management of ECHO data quality summaries belongs to Data Partners.– Update Reverb & coordinate w/ ECHO Ops to accurately configure DQSs.

REVERB TECHNICAL OVERVIEW

Implementation Notes

• Implemented using an Agile Process• Implemented using Ruby on Rails, HTML,

CSS, JavaScript• Mostly built on top of new ECHO REST API

– Remainder will be moved to Multiformat REST API late summer

• Implementation time and team– ~10 months– ~6 developers

Maintainability

WIST Reverb + REST0

50,000

100,000

150,000

200,000

250,000

300,000

Approx. Lines of Code

Maintainability

@javascriptFeature: Spatial search for datasets In order to narrow my dataset results by spatial bounds as a Reverb user I should be able to visually select boundaries for my dataset searches

Scenario: Type in a valid polygon Given I am on the home page When I select "Polygon" from "spatial_type" within ".spatial-field" And I wait for datasets to load When I fill in "spatial" with "-9.102, 40.430, 22.594, 22.852, -1.406, 1.055" within ".spatial-field" And I wait for datasets to load Then I should find the dataset with id "Dataset with normal cartesian bounding rectangle" And I should find the dataset with id "Dataset with normal cartesian polygon" And I should not find the dataset with id "Dataset with cartesian point”

• Nearly all testing is fully automated• Unit Tests using Test::Unit• Integration Tests using Cucumber,

Capybara, and Celerity

ECHO DBECHO DB

Deployment Model

ECHO Kernel(SOAP API)

ECHO Kernel(SOAP API)

REST API REST API

Reverb Reverb

ECHO DB

Reverb is deployed to

multiple serversUsers are transparently

balanced across instances

Reverb distributes its search and order load

across all ECHO kernels

Reverb takes advantage of ECHO’s ability to distribute

across DB nodes

Like ECHO, Reverb can be updated

without downtime.

Supported Browsers

• Officially supported– Firefox– IE7 and IE8– Safari on OS X

• Unofficially tested– Firefox 4.x– Chrome 11– Safari 5.x

Supported Browse Image Types

• Reverb will automaticallydisplay browser friendly types (JPG, PNG, etc.)

• Reverb can detect HDFbrowse and automatically extract embedded JPGs

• Multiple browse images are support and fetched asynchronously for performance

Supported Spatial Projections

• Searching– Google Maps Mercator– North/South Polar Stereographic

• Subsetting Projections– North/South EASE-Grid (EPSG:3408, EPSG:3409)– Hughes / NSIDC North/South Polar Stereographic

(EPSG:3411, EPSG:3412)• Spatial Extent Visualization (results)

– OpenLayers– Plate Carree (equirectangular)– North/South Polar Stereographic

Spatial extent drawing

• Reverb can render multiple granule spatial extents

• Will provide swath and polar rendering before release

WIST 2 REVERB TRANSITION

WIST To Reverb Migration

• EDG to WIST Recap– Accounts migrated from EDG instances to ECHO requiring user actions.– DAAC USO involvement to notify users encouraging self-migration.– Self-Migration tool developed and made available by ECHO team.– Password reset required during migration

• WIST to Reverb Preparation & Execution– No account migration activities required.– Users may self migrate to Reverb on their own.– WIST & Reverb usage will continue to be monitored.

• Discussion– How should we advertise the Operational Reverb on WIST?– How can we encourage users to self-migrate?– What criteria should be considered for starting a forced migration?– How is the final migration enforced?

REVERB FUTURE CHANGES

MULTI-FORMAT INGEST REST API INTEGRATION

MultiFormat Reverb Integration

ECHO DBECHO DB

ECHO Kernel(SOAP API)

ECHO Kernel(SOAP API)

REST API REST API

Reverb Reverb

ECHO DB

V2 REST API V2 REST APIECHO DBECHO DBElastic Search IndexECHO DBECHO DBElastic Search Index

Reverb Enhancements

• Multiformat REST will immediately provide Reverb with– Better and more complete Keyword Searching– Full and accurate hit counts– Ability to search metadata in a native ECHO 10 or

ISO19115 format– Retrieve metadata in ECHO10, Atom, or ISO19115– More advanced facets (valids) support

• Multiformat REST sets the stage for advanced Reverb feature such as– Able to display format specific information such as

production history and citations– Relevancy sorting

BROWSE VISUALIZATION ENHANCEMENTS

Temporal Browse Visualization

Dataset 1

Dataset 2

Dataset 3

(Non-artist’s rendering…)

5/21/20116/7/2011

Browse “cover-flow”(Non-artist’s rendering…)

SSW/ESI Integration

• SSW Integration– Targeting interaction with services exposing SSW API– Initially integration work with LPDAAC & GES DISC– Additional service integration to follow initial integration effort– Form development will require manual intervention & configuration– Development not currently scheduled in an ECHO sprint

• EOSDIS Service Interface (ESI) Integration– Participating in bi-weekly ESI technical meeting– Integration work coordinated with ECS DAACs– Investigating Automated Dataset Configuration -> ECHO Form Translation– Development to be scheduled in late-summer 2011

Client Technology Sharing

• Survey Inputs– Existing EOSDIS clients surveyed & discussions held w/ some DAACs regarding

technologies & workflows that could be incorporated into Reverb.– Specific requests received from LPDAAC regarding client modifications.

• Current Items in Discussion– Import Shapefile defined boundary for spatial searching– Ops Concept Development - Tile layout view in granule results (GloVis-esque)– Ops Concept Development - Drill-Down selection (Mosaic Pivot Viewer)– Location Search (Google Maps Point)– Location Search w/ Pre-Compiled Shape Files (e.g. Country, State, County)– User Preferences (e.g favorite queries, option selections, etc)– Export Results to KML– Map-Based tile selection for spatial searching

• Other Suggestions?

Notable NCRs

• Reverb Enhancements– Spatial Entry Enhancements

• Advanced Text Entry• Zoom to selection• Lat/Lon Cursor Tracking

– Show temporal information in granule results row– Order Option Enhancements (e.g. Editing, Default, & Multiple Products)– Filter & search w/ multiple temporal ranges– Filter & search w/ multiple tile ranges– Display granule spatial extents on 3D globe

Advanced Concepts

• Discovery– Display total granules found– Fluid granule list expansion – Display search area and/or granule spatial extents on a 3D globe– Additional projections during spatial selection

• Ordering & Downloading– Group granules by dataset during order workflow– Group by dataset & search constraints in cart– Bulk Order Processing– Advanced URL Downloading

• Online Resource URLs• OPeNDAP vs Direct Access• Metadata URLs (Format Specific)

– Additional projections during spatial subsetting