[Esip-discovery] Impact of Discovery services
Mattmann, Chris A (388J)
chris.a.mattmann at jpl.nasa.gov
Thu Mar 10 11:06:11 EST 2011
We just used the default SOLR Response Writers (one of which is RSS, and others being XML, JSON, etc.) on those projects. In some prior projects, I did use Apache Nutch's OpenSearch response writer (circa 2005) and found it to be quite effective:
Here's some docs on the SOLR Response Writers:
It would be really useful to write an ESIP Federated Search response writer and maybe contribute it back to the SOLR community so that downstream users of SOLR (us and any other NASA project) could get the ESIP Federated Search protocol for free.
to track this.
On Mar 10, 2011, at 7:34 AM, Lynnes, Christopher S. (GSFC-6102) wrote:
> Did either of those efforts use OpenSearch and/or the ESIP Federated Search conventions? If not, any thought about migrating to those conventions?
> On Mar 10, 2011, at 12:19 AM, Mattmann, Chris A (388J) wrote:
>> Hi Guys,
>> I've been part of two efforts in the Discovery service arena:
>> 1. for the NASA Virtual Oceanographic Data Center project, where we focused on NASA and NOAA oceanographic datasets (NVODS, OSTM, PO.DAAC), and making them available via a Solr facet+free text search. http://vodc.jpl.nasa.gov. This was an ACCESS 2007 funded project.
>> 2. for the NASA Coastal Marine Discovery Service (CMDS), where we are extending on our VODC work, and focusing mostly on coastal ocean datasets (fisheries, etc.), looking at e.g., ERRDAP, Coastwatch, etc., and focused on linking the data into the EasyGIS system. This is an ACCESS 2009 project.
>> Both #1 and #2 include the use of Apache Solr, and Apache OODT search services.
>> On Mar 9, 2011, at 4:58 AM, Lynnes, Christopher S. (GSFC-6102) wrote:
>>> On Mar 8, 2011, at 2:50 PM, Hua, Hook (388C) wrote:
>>>> 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?
>>> Also, we should distinguish between server and client implementations. Here at GES DISC, we have implemented:
>>> (1) server - Mirador
>>> (2) client - Mirador cross-data center search
>>> (3) client - Giovanni
>>> (4) client - Simple Subset Wizard
>>>> (2) Have there been any improvements to data and service discovery/access?
>>> Not sure what to put for this--can you provide an example or two?
>>>> We could get a good start on (1). Some wiki pages were setup with listings
>>>> of Discovery services and clients. Some people have already begun submitting
>>>> entries. But we want to invite more to submit your deployed or
>>>> in-development Discovery services/clients. These are not meant as an
>>>> official registry, but rather meant to give ourselves a better understanding
>>>> of who has or is implementing what.
>>>> Esip-discovery mailing list
>>>> Esip-discovery at lists.esipfed.org
>>> Christopher Lynnes
>>> Goddard Earth Sciences Data and Information Center, NASA/GSFC
>>> Esip-discovery mailing list
>>> Esip-discovery at lists.esipfed.org
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann at nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
> Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann at nasa.gov
Phone: +1 (818) 354-8810
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
More information about the Esip-discovery