Semtools: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362011-04-04T21:30:41ZEcoinformatics Redmine
Redmine Bug #5371 (New): AnnotationManager: query performancehttps://projects.ecoinformatics.org/ecoinfo/issues/53712011-04-04T21:30:41Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Identify long-running aspects of semquery. First glance indicates that returning the metadata/annotation content to be displayed in Metacat is the biggest bottleneck. This is good and bad. It means using the DB for managing annotations is pretty efficient, but it also means that returning large results sets will not be so efficient.<br />Probable solution: include only a subset of annotation information in the resultset rather than the entire annotation xml content.</p> Bug #5368 (New): Compound query conditionshttps://projects.ecoinformatics.org/ecoinfo/issues/53682011-04-04T21:05:18Zben leinfelderleinfelder@nceas.ucsb.edu
<p>We allow grouping of semantic query conditions, but not in the web UI. Adding grouping makes the UI much more complicated, but allows exact query authoring. We've taken a simpler approach that is largely based on browsing and drilling down iteratively after applying a set of conditions (thereby making an implicit intersection of the criteria and their results).<br />This is a place-holder bug to track whether we need to support super-expressive compound grouping.</p> Bug #5367 (New): Verify "same observation as" query criteriahttps://projects.ecoinformatics.org/ecoinfo/issues/53672011-04-04T21:02:40Zben leinfelderleinfelder@nceas.ucsb.edu
<p>The "strict=true" query condition mode indicates that the criteria in that group must come from the same observation in order to be considered true. During testing, we should make sure that the query results reflect the desired distinction is being made.</p> Bug #5366 (New): Integrate semantic query with keyword and spatial queryhttps://projects.ecoinformatics.org/ecoinfo/issues/53662011-04-04T20:53:23Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Combining semantic, keyword and spatial criteria will allow a smoother transition from non-semantic metadata to semantically annotated data. It will also allow us to refine query results further by limiting to specific organizations, locations, people, etc.</p>
<p>Metacat should support combining "squery", "semquery" and "spatialquery" actions in an extensible way that lets future query mechanisms contribute conditions to the query so that additional (or fewer) matches are returned.</p>
<p>This may require additional or wrapper syntax for specifying a compound, multi-faceted query.</p> Bug #5365 (New): Context-based semantic queryhttps://projects.ecoinformatics.org/ecoinfo/issues/53652011-04-04T20:48:07Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Include interace for expressing context criteria for a semantic query. The query syntax allows context criteria, but there is no GUI for it. The criteria assume a basic context template rather than any specific entity (because of the general nature of the query there is not a concrete observation before submitting the query). Context is defined as <Entity> <Relationship> <Entity> and can be combined to further expand/refine context conditions. The classes are expanded using the ontology as you would expect.</p>