Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362005-06-10T17:33:13ZEcoinformatics Redmine
Redmine Bug #2105 (New): add taxon concept search for datahttps://projects.ecoinformatics.org/ecoinfo/issues/21052005-06-10T17:33:13ZLaura Downeyldowney@lternet.edu
<p>add capability to do taxon concept searches (remote, local too?)</p>
<p>[decision from May 2005 Estes Park mtg]</p> Bug #2104 (New): add concept search for datahttps://projects.ecoinformatics.org/ecoinfo/issues/21042005-06-10T17:31:59ZLaura Downeyldowney@lternet.edu
<p>add concept search for data (works on both local and remote data)</p>
<p>[decision from May 2005 Estes Park mtg]</p> Bug #2033 (New): provide indication of actor compatibilityhttps://projects.ecoinformatics.org/ecoinfo/issues/20332005-03-11T21:02:25ZLaura Downeyldowney@lternet.edu
<p>provide some indication to user of actor compatability, e.g, if they have some <br />actor selected, somehow indicate to them which actors can be hooked up to the <br />currently selected actor</p> Bug #2015 (New): Provide more meaningful error messageshttps://projects.ecoinformatics.org/ecoinfo/issues/20152005-03-11T18:57:43ZDan Higginshiggins@nceas.ucsb.edu
<p>Suggested by Laura Downey<br />User oriented error messages needed (rather than stack traces?)</p> Bug #1997 (New): Support Getting Metadata for Darwin Core search result itemhttps://projects.ecoinformatics.org/ecoinfo/issues/19972005-03-01T18:49:40ZJing Taotao@nceas.ucsb.edu
<p>In data search result panel, we add a new right click button for getting<br />metadata for the item. But currently we only support eml200 and eml201. We need<br />also support DarwinCore search result too. First we need create a style sheet to<br />transfer Darwincore xml to html.</p> Bug #1981 (New): Extend database query actor to handle datatypeshttps://projects.ecoinformatics.org/ecoinfo/issues/19812005-02-16T01:24:37ZEfrat Jaegerjaeger@ecoinformatics.org
<p>Currently return a string representation of the output. Should be extended to <br />specify the type of the 'string' output as well.</p> Bug #1923 (New): Develop ontologies; engage KR grouphttps://projects.ecoinformatics.org/ecoinfo/issues/19232005-01-25T19:11:27ZShawn Bowersbowers@gonzaga.edu
<p>Develop some guidelines for what makes an ontology useful for specific SMS<br />applications so that the KR group can develop appropriate ontologies.</p>
<p>Pick a few actors that could be useful to us and use those to create the<br />ontologies used to annotate ports, rather than from first principals. In<br />particular, use Eco Niche Modeling example and Biodiversity Analysis example<br />from SEEK.</p>
<p>Determine how to deal with actors that use files for passing data rather than<br />passing the data itself.</p> Bug #1922 (New): Develop strategies for GUI extenstions for the semantics stuffhttps://projects.ecoinformatics.org/ecoinfo/issues/19222005-01-25T19:07:45ZShawn Bowersbowers@gonzaga.edu
<p>Determine whether the "access points" at higher levels of the GUI can be<br />modified to suit our needs, rather than change thier classes through their Moml<br />extension mechanisms. Alternatively, generalize the Ptolemy source code for<br />extended GUI customization.</p> Bug #1921 (New): Define the Kepler GUI components required for semantic mediation in Keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/19212005-01-25T19:06:05ZShawn Bowersbowers@gonzaga.edu
<p>For example, a new button for "semantic type check", a easy mechanism to add<br />semantic annotations to actors/ports and possibly datasets, and an explanation<br />interface for describing why a particular item was found/used/merged, etc.</p> Bug #1920 (New): Search based on semantic annotations of a dataset's attributeshttps://projects.ecoinformatics.org/ecoinfo/issues/19202005-01-25T19:02:04ZShawn Bowersbowers@gonzaga.eduBug #1919 (New): choose language for semantic annotations in kepler archiveshttps://projects.ecoinformatics.org/ecoinfo/issues/19192005-01-25T19:00:13ZShawn Bowersbowers@gonzaga.eduBug #1918 (New): Search based on the semantic annotation of an actor's porthttps://projects.ecoinformatics.org/ecoinfo/issues/19182005-01-25T18:59:11ZShawn Bowersbowers@gonzaga.eduBug #1917 (New): Design and implement workflow semantic type check.https://projects.ecoinformatics.org/ecoinfo/issues/19172005-01-25T18:57:59ZShawn Bowersbowers@gonzaga.edu
<p>Design and implement a feature similar to the Kepler type-system check (which<br />occurs after a workflow is executed), but for semantic annotations.</p>
<p>The semantic type-check should be a component (api) that can be called by<br />Kepler. Need a mechanism to report (through an interface) the semantic problems<br />of a workflow (if any exist), and possibly a mechanism to suggest ways to<br />correct the problems (a la the unit type system).</p> Bug #1916 (New): Implement semantic search for data and actors in local fileshttps://projects.ecoinformatics.org/ecoinfo/issues/19162005-01-25T18:54:03ZShawn Bowersbowers@gonzaga.edu
<p>The goal of this work is to decouple the semantic search as much as possible<br />from Kepler so we can shift the implementation to EcoGrid nodes and other remote<br />repositories.</p>
<p>Investigate whether it is feasible to combine the actor and data simple search<br />interfaces into a single set of search interfaces, that do not distinguish<br />between different object types.</p>
<p>Also, the resulting implementation should provide actor and data "smart" search<br />so that the implementations locally and remotely are the same.</p> Bug #1915 (New): Define a published interface for a semantic search servicehttps://projects.ecoinformatics.org/ecoinfo/issues/19152005-01-25T18:49:32ZShawn Bowersbowers@gonzaga.edu
<p>The purpose of this work is to define a generic api for "smart" search, which<br />implementation(s) will conform to. Each api operation will require both (1) a<br />public interface that external services will interface with (to call the desired<br />function), and (2) a description of the required backend information-storage<br />operations necessary to execute the desired functions. For example, this might<br />include the operation 'getObjectLSIDList(ObjectType) : ObjectLSIDList' that when<br />given an object type (such as "actor" or "dataset") will return all the LSIDs<br />for objects stored in the target backend repository.</p>