[seek-dev] Ecogrid Registry and Query

[Rod Spears]

I have the initial implementation of the Ecogrid Registry working.

To try it out:
http://129.237.201.166:8080/ogsa/registry.jsp

You can try out a Digir Query by going to the Query Page 
<http://129.237.201.166:8080/ogsa/query.jsp> and selecting the "Digir 
Ecogrid Resource" and then copy/paste this query into the text box:

<egq:query queryId="query-digir.1.1" system="http://knb.ecoinformatics.org"
    xmlns:egq="ecogrid://ecoinformatics.org/ecogrid-query-1.0.0beta1"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    
xsi:schemaLocation="ecogrid://ecoinformatics.org/ecogrid-query-1.0.0beta1 
../../src/xsd/query.xsd">
    <namespace 
prefix="darwin">http://digir.net/schema/conceptual/darwin/2003/1.0</namespace>
    <returnfield>/ScientificName</returnfield>
    <returnfield>/Longitude</returnfield>
    <returnfield>/Latitude</returnfield>
    <title>Peromyscus genus query</title>
    <condition operator="LIKE" concept="Genus">Peromyscus</condition>
</egq:query>

The results should look like this:
Query succeeded!
darwin:ScientificName 	darwin:Longitude 	darwin:Latitude
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS MANICULATUS LUTEUS 	null 	null
PEROMYSCUS LEUCOPUS NOVEBORACENSIS 	null 	null
PEROMYSCUS CALIFORNICUS PARASITICUS 	null 	null
PEROMYSCUS CALIFORNICUS PARASITICUS 	null 	null
PEROMYSCUS CALIFORNICUS PARASITICUS 	null 	null


It is my intention to have a more WYSIWYG way of entering a query. But 
for now this works.

When you click on "Submit" for the query, it looks the resource name up 
in the registry and then makes a call to that resource with the query. I 
am not why sure Metacat doesn't work, maybe the service wasn't working 
when I tried it out (but it should because this is all generic)

Intersting points:

   1. The registry currently sits on top of a flat file database, we can
      put it on top of anything we want later.
   2. The JSP pages use a Java Bean to make the actual calls to Globus
   3. I initially got this all working using generic SOAP calls because
      Globus has been so unpredicatable in terms of getting things to
      work. My previous version (before checking in) used a factory to
      create a SOAP Bean or a Globus bean and could access the
      functionality through either via a generic interface.
   4. I wrote all the SOAP code and got it working in less than 2 days.
      Writing a Globus service from scratch and getting it working
      (without security) has taken over a week and a half to two weeks.
   5. Globus is the worst documented piece of software I have used in my
      entire career, it is also the most fragile, and hardest to
      configure. But then everyone knows how I feel about Globus ;-) .
   6. I am a step away from having the Registry engine distrubute itself
      to other Registry "Nodes" (I actually had that working using SOAP,
      but I have it disabled at the moment)

Give it a try and let me know,
Rod

-- 
Rod Spears
Biodiversity Research Center
University of Kansas
1345 Jayhawk Boulevard
Lawrence, KS 66045, USA
Tel: 785 864-4082, Fax: 785 864-5335

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/seek-dev/attachments/20040310/400f8b93/attachment.htm