Project

General

Profile

Actions

Bug #4890

closed

findMatchingAnnotations(...) needs Context

Added by ben leinfelder over 14 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Category:
Morpho Plugin
Target version:
Start date:
03/17/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4890

Description

Likely the first of many enhancements to the AnnotationManager API.
We need to allow searching based on Context.

<Entity> <Relationship> <Entity>
--
"Tree" "withIn" "Plot"


Related issues

Blocked by Semtools - Bug #4889: Compound Search UIResolvedben leinfelder03/17/2010

Actions
Actions #1

Updated by ben leinfelder over 14 years ago

[4:31pm] bowers: i think the madlib stuff could be reused for this ... although you might want a way to say that two observations are the same
[4:32pm] bowers: E.g., a query might be:
[4:32pm] bowers: I want datasets where:
[4:32pm] bowers: -- the height of a plant was recorded using the meter standard
[4:32pm] bowers: -- the dryweight of a plant was recorded using the gram standard
[4:33pm] bowers: -- a plant was recorded within a plot
[4:33pm] bowers: -- a plot was recorded within a site
[4:34pm] bowers: actually the last two ml's would be:
[4:34pm] bowers: -- the plant was within the plot
[4:34pm] bowers: -- the plot was within the site
[4:34pm] bowers: the issue here would be how do datasets match this?
[4:35pm] bowers: e.g., what if I have two different plants, where for one the height was measured, and for the other the dryweight was measured
[4:35pm] bowers: similarly, which plant was within the plot

Actions #2

Updated by ben leinfelder over 14 years ago

now you can provide a list of Triples (Entity, Relationship, Entity) as part of the search criteria.

Actions #3

Updated by ben leinfelder over 14 years ago

Reopening but as a Morpho plugin bug.
Now that the annotation manager can search on context, we need to include it in the UI

Actions #4

Updated by ben leinfelder over 14 years ago

added to the UI.
One thing that could be improved is integration between the Observation Entity selection and the first Context Entity selection - they should probably be condensed into a single field, or at least their values should be synchronized.

Actions #5

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 4890

Actions

Also available in: Atom PDF