[Esip-discovery] ESIP Discovery Cluster Telecon, Tuesday, Feb 12 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT
Hua, Hook (388C)
hook.hua at jpl.nasa.gov
Tue Feb 12 14:29:08 EST 2013
This is also related to the multiple search term boolean behavior we had
discussed at the Winter meeting. We had said the default behavior would be
"AND" unless specified. This aspect was also added to our implementation
coverage document  to see what is implemented.
We have been using Solr as our backend OpenSearch implementation and find
it useful that it provides a configuration based approach to defining a
default behavior when no AND/OR/+/- are specified.
On 2/12/13 10:09 AM, "Huang, Thomas (388J)" <Thomas.Huang at jpl.nasa.gov>
>PO.DAAC operation is in the process of deploying our next update to our
>portal search which is equipped with google-like search syntax including
>phase search. We are leveraging on the built-in support from Solr.
>Should we consider a DCP for this?
>I won't be able to attend today's telecon due to another meeting
>conflict. Nga Chung will be dialing in.
>On Feb 12, 2013, at 8:38 AM, Mattmann, Chris A (388J) wrote:
>> Just an FYI, in Lucene/Solr they would satisfy this with the query:
>> air temperature "air temperature"
>> Which would match documents with either air, or temperature or both air
>> and temperature appearing next to one another.
>> On 2/12/13 5:07 AM, "Lynnes, Christopher S. (GSFC-6102)"
>> <christopher.s.lynnes at nasa.gov> wrote:
>>> On Feb 11, 2013, at 4:24 PM, Eric Rozell <rozele at rpi.edu> wrote:
>>>> Hi Everyone,
>>>> The next Discovery cluster telecon is tomorrow, Tuesday, Feb 12 at
>>>> ET. Agenda and call details are below and posted on the wiki. Please
>>>> reply or add to the agenda if any other topics should be discussed.
>>>> Regards -
>>>> € Status of RFC
>>>> € Proposal for returning collection level data access points
>>>> € Other topics
>>> Got a late-breaking topic here:
>>> Yoshiyuko Kudo pointed out to me that there is no standardization and
>>> little support for phrase search, e.g., the phrase "air temperature".
>>> This is a good canary-in-a-coal-mine phrase for our discipline because
>>> "air" and "temperature" can coexist in many datasets that do not have
>>> "air temperature", so even the logical AND is not enough.
>>> So if we were to adopt this as a requirement in our convention: would
>>> any search providers be unduly burdened by this requirement, or is it
>>> just a matter of some extra configuration and indexing in the search
>>> engines being used?
>>>> Call Details
>>>> To start or join the online portion of the meeting:
>>>> € Click join next to the meeting name. (Note: If the meeting has not
>>>> yet started, join will not be visible, and it will say 'Display Info'.
>>>> Wait a minute and refresh screen)
>>>> € Enter your name and email address
>>>> € If you are asked for a password, enter the access code: 231 407 50
>>>> with no spaces or #.
>>>> To join the audio portion of the Conference meeting:
>>>> Call-in toll-free number (US/Canada): 1-877-669-3239
>>>> Attendee access code: 231 407 50#
>>>> Esip-discovery mailing list
>>>> Esip-discovery at lists.esipfed.org
>>> Dr. Christopher Lynnes, NASA/GSFC, ph: 301-614-5185
>>> Esip-discovery mailing list
>>> Esip-discovery at lists.esipfed.org
>> Esip-discovery mailing list
>> Esip-discovery at lists.esipfed.org
>Jet Propulsion Laboratory
>4800 Oak Grove Drive, Mail Stop 171-264, Pasadena, CA 91109
>Phone: 818.354.2747, Cell: 626.318.4637, Email: thomas.huang at jpl.nasa.gov
>DISCLAIMER: All personal and professional opinions presented herein are
>my own and do not, in any way, represent the opinion or policy of JPL,
>NASA or Caltech.
>Esip-discovery mailing list
>Esip-discovery at lists.esipfed.org
More information about the Esip-discovery