SEEK: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-06-09T18:32:12ZEcoinformatics Redmine
Redmine Bug #3387 (New): ontology validationhttps://projects.ecoinformatics.org/ecoinfo/issues/33872008-06-09T18:32:12ZChad Berkleyberkley@nceas.ucsb.edu
<p>when an ontology is uploaded to metacat it should be validated in several ways (in addition to the xml validation that metacat already does):</p>
<ul>
<li>if it references other documents, the user should be asked to upload those documents as well.</li>
<li>referential integrity should be checked</li>
<li>owl validitiy should be checked</li>
</ul>
<p>Any errors should be reported back to the user.</p> Bug #3386 (New): ontology management with metacathttps://projects.ecoinformatics.org/ecoinfo/issues/33862008-06-09T18:17:33ZChad Berkleyberkley@nceas.ucsb.edu
<p>User should be able to browse ontologies in the system. Should also be able to update existing ontologies.</p> Bug #3112 (New): Deploy ecogrid-1.0.0 services for DiGIR and enforce namespaceshttps://projects.ecoinformatics.org/ecoinfo/issues/31122008-01-30T18:52:54Zben leinfelderleinfelder@nceas.ucsb.edu
<p>It was originally thought that the change in ecogrid namespaces (beta to 1.0) would be incompatible with the current DigirQueryService deployment (using beta namespaces). This appears not to be the case (they work together!) But, really, the namespaces <em>should</em> be enforced.<br />When the enhancements for doing faster (cached?) and better (dynamic providers listing?) digir queries are ready, we should deploy an updated version of this service.<br />Dave Vieglais sounds keen on this and will assist.</p> Bug #2301 (New): deploy ecogrid-1.0.0beta2 services for metacat, srb, digir, geonhttps://projects.ecoinformatics.org/ecoinfo/issues/23012005-11-29T21:28:11ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to coordinate the deployment of the beta2 release so that all services are<br />deployed at the same time. Deployment really can not occur until all of the<br />migration to web services bugs are complete (bug 2294, bug 2295, bug 2296, bug<br />2297, bug 2298).</p> 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 #2276 (New): Investigate security facilities for Web Serviceshttps://projects.ecoinformatics.org/ecoinfo/issues/22762005-11-16T18:15:54ZKevin Rulandkruland@ku.edu
<p>Investigate methods to add secuirty to Web Services (Ecogrid) and formulate a<br />recommendation. Must support certificate based authentication. Explore<br />alternatives which use explicit security vs implicit security.</p> Bug #1638 (New): EcoGrid Web - Implementationhttps://projects.ecoinformatics.org/ecoinfo/issues/16382004-07-14T14:59:09ZSteve Tekellstekell@lternet.edu
<p>Implement the EcoGrid search webapp.</p> Bug #1637 (New): EcoGrid Web - Designhttps://projects.ecoinformatics.org/ecoinfo/issues/16372004-07-14T14:52:43ZSteve Tekellstekell@lternet.edu
<p>Design web application for searching EcoGrid.</p>
<p>The search should be able to search multiple nodes at once and present the <br />results in a single set.<br />The search should be able to search more than one format (EML, Darwin) <br />transparently (to the user).<br />Search results should support multiple styles (skins).<br />Possibly have a basic and advanced query inputs, where basic is a single <br />step/screen with one or a few fields and advanced is multiple steps or sets of <br />fields.<br />The search funtionality will be similar to Morpho with the significant <br />difference of handling multiple nodes and formats.<br />The EcoGrid Webapp will utilize existing web services (or grid services), <br />which can handle single nodes and a single format.</p>
<p>More details can be found on the SEEK Wiki, EcoGridWeb, EcoGridWebDesign pages.</p> Bug #1377 (In Progress): Create UML diagram from stubshttps://projects.ecoinformatics.org/ecoinfo/issues/13772004-03-23T21:50:26ZAimee Stewartastewart@ku.eduBug #1375 (In Progress): Add deployment target to ant build filehttps://projects.ecoinformatics.org/ecoinfo/issues/13752004-03-23T21:35:36ZAimee Stewartastewart@ku.eduBug #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 #1163 (New): install and configure certificate authority system for ecogridhttps://projects.ecoinformatics.org/ecoinfo/issues/11632003-09-26T21:43:59ZMatt Jonesjones@nceas.ucsb.edu
<p>We need a common mechanism for authenticating users for EcoGrid. We have<br />general agreement that the OGSA Grid Security Infrastructure (GSI) is the right<br />way to handle this. For that to work, every user needs to have a public key<br />certificate which is signed by a certificate authority (CA). In Seattle Sept 23<br />the EcoGrid team agreed that the best way to handle this is through a<br />hierarchichal certificate granting structure. A root EcoGrid CA will sign<br />certificates for various organizations such as LTER and NCEAS, and they in turn<br />will sign certificates for users in their organization. This 'chain-of-trust',<br />if properly managed, should establish strong security and be scalable to the ><br />5000 scientists in our current personnel directories.</p>
<p>Each of these trusted CA's would probably also act as one of the distributed<br />EcoGrid Registries for locating services throughout the grid.</p>
<p>For this to work, we need a simple system in place for users to request<br />certificates and for the CA admins to sign them. Matt agreed to tackle this.</p>
<p>The tricky issues remaining here include:<br /> 1) What system can be used for distributing DN info to mapfiles?<br /> 2) How can browser-based interfaces be used with certificates?</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>