[Esip-discovery] Impact of Discovery services
Hua, Hook (388C)
hook.hua at jpl.nasa.gov
Fri Mar 18 02:21:19 EDT 2011
Thanks for posting.
We've got a good start in our Discovery listings now:
# of OpenSearch services: 5
# of DataCasting services: 3
# of ServiceCasting services: 1
# of various Discovery clients: 10
Your client_id approach to track metrics is interesting. It brings up a fascinating look at the variety of REST Request parameters used, as well as the variety of different formats used for OSDDs:
It might be good for the Cluster to begin work on standardizing something on this front...
From: esip-discovery-bounces at lists.esipfed.org [esip-discovery-bounces at lists.esipfed.org] On Behalf Of Cechini, Matthew F. (GSFC-423.0)[RAYTHEON COMPANY] [matthew.f.cechini at nasa.gov]
Sent: Thursday, March 17, 2011 10:26 AM
To: esip-discovery at lists.esipfed.org
Subject: Re: [Esip-discovery] Impact of Discovery services
Recreating a reply since I wasn't on the list when this message was initially sent:
>It would be useful to eventually get an assessment of the impact of
>Discovery services to the community. More specifically, to be able to answer
>these two questions:
>(1) Where Discovery services have been implemented and deployed?
I have updated the wiki with information regarding our ECHO-ESIP API and sample Html client.
>(2) Have there been any improvements to data and service discovery/access?
Not sure if it's what you're looking for, but the attached document contains a brief overview regarding our ECHO-ESIP API's ability to generate dynamic OSDDs. We needed this in order to embed a client_id for metrics, but did not want to force the introduction of a required request parameter.
Matthew F Cechini
ECHO Operations Lead - Systems Engineer
Office: (301) 851-8049
Cell : (202) 251-8013
Fax : (301) 851-8283
E-Mail: Matthew.F.Cechini at nasa.gov<mailto:Matthew.F.Cechini at nasa.gov>
More information about the Esip-discovery