SEEK: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362005-11-29T20:20:38ZEcoinformatics Redmine
Redmine Bug #2293 (In Progress): DiGIR ecogrid support for multiple Darwin Core versionshttps://projects.ecoinformatics.org/ecoinfo/issues/22932005-11-29T20:20:38ZMatt Jonesjones@nceas.ucsb.edu
<p>Darwin Core comes in at least two incompatible versions, but these two versions<br />share the same namespace (even though their schemas differ in significant ways).<br /> We need EcoGrid queries to be able to handle multiple DarwinCore schemas,<br />probably by differentiating them by testing for known elements in each result.</p> Bug #2292 (In Progress): out of memory problems on DiGIR EcoGrid implementationhttps://projects.ecoinformatics.org/ecoinfo/issues/22922005-11-29T20:14:33ZMatt Jonesjones@nceas.ucsb.edu
<p>When resultsets are large, the DiGIR implementation can run out of memory. This<br />is a problem related to how the resultset is built up in memory and needs to be<br />fixed to support arbitraily large (or at least very large) result sets.</p> Bug #2291 (New): define faults for all EcoGrid serviceshttps://projects.ecoinformatics.org/ecoinfo/issues/22912005-11-29T20:12:02ZMatt Jonesjones@nceas.ucsb.edu
<p>The current API needs to be modified to be able to pass back faults for error<br />conditions. To close this bug, we need to:</p>
<p>1) design an intelligent set of faults that covers conceivable error conditions<br />and provides a human readable message appropriate for display to users<br />2) add these faults to the WSDL definitions of the ecogrid apis, making sure to<br />support both SOAP and HTTP bindings where they exist<br />3) implement the faults for each of the services (metacat, digir, srb)</p> Bug #1166 (In Progress): create a schema for registry metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/11662003-09-26T22:09:19ZMatt Jonesjones@nceas.ucsb.edu
<p>Need a schema that defines the metadata associated with an EcoGrid Registry. <br />Minimally this is the GSH of the registry, but it also will likely include other<br />information, such as contact info for the maintainers, and mechanisms to get<br />lists of the services registered there (probably already part of the ogsa<br />registry interface). Matt agreed to start this, and Raja will review it.</p> Bug #1059 (New): create testing harness for ecogridhttps://projects.ecoinformatics.org/ecoinfo/issues/10592003-05-19T19:57:31ZMatt Jonesjones@nceas.ucsb.edu
<p>We need a common testing harness that can be used to launch client queries<br />against ecogrid nodes and validate that the results returned are correct. This<br />system would be a basic client application, and so the core of it could be<br />reused in other clients if it is properly designed.</p>
<p>Who: Higgins<br />Target: June 9</p>