ECHO 10.0 Supplementary Specification PDF (328 KB)
ECHO 10.0 Supplementary Specification (Ingest) PDF (356 KB)
ECHO 10.0 Metadata Requirements & Recommendations PDF (213 KB)
Features & Functionality
Ingest
Support the revised ECS ingest delivery algorithm
Reduce lag time from when ECHO receives provider metadata to availability in ECHO
Improve database resiliency to software bugs, unexpected or corrupt data, and uncontrolled environmental faults
Improve ingest usability including e-mail and reporting messages
Catalog: ECHO shall support multi-orbit searches on granules
ECHO shall ingest granules that are defined by more than one orbit
ECHO queries shall support spatial queries on granules that are defined by more than one orbit
ECHO data model shall accurately capture multi-orbit information as required to support the selected multi-orbit query implementation
ECHO shall support returning multi-orbit metadata when retrieving the results of a successfully executed AQL query
ECHO shall continue to support ingest, query, and retrieval of non-multi-orbit data without modification
Catalog: ECHO Collection Version ID shall support alphanumeric based version IDs
ECHO shall support ingesting an alphanumeric version ID
ECHO shall support querying an alphanumeric version ID
ECHO shall support returning results containing an alphanumeric version ID
Ingest shall save a Version ID as an alphanumeric string
Queries shall be able to
(1) Search by a collection's version ID
(2) Handle the collection's version ID as a character string
(3) Include the collection's version ID in all results, even if not searched
The retrieval of query results shall
(1) Include the collection's version ID in all results
(2) Handle the collection's version ID as an alphanumeric string
The ECHO data model must store the collection's version ID as an alphanumeric string
The existing data (collection's version ID) shall be converted to an alphanumeric string
User Service
ECHO 10.0 will assume the responsibility for SMC user accounts as part of the ECS modernization effort. ECHO 10.0 must sufficiently match the ECS User Profile as to allow migration of existing SMC user accounts to ECHO
Required User Profile fields will be consistent with ECS required fields
Security
ECHO shall implement ways to minimize the exposure to and the impact of typical security attacks including, but not limited to SQL Injection, Denial of Service (DoS), and Cross Site Scripting (XSS)