Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #1741 (closed)

Opened 14 years ago

Closed 14 years ago

Linking Images and ROI

Reported by: dzmacdonald Owned by: jamoore
Priority: major Milestone: OMERO-Beta4.2
Component: Model Keywords: ImageImageLink, Annotations
Cc: jamoore, wmoore, jburel Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description

Linking Objects

There is a requirement from the users that there should be a mechanism to link images to other images, roi to roi and roi to images. This mechanism should also allow some logic to be placed on the link describing the relationship between objects. The relationship should have a qualifier defining what created that relationship.

As a first draft the relationships will be defined by a predicate, a list of the initial predicates are:

  • Associate
  • Aggregate
  • Compose
  • Derive

The link should also have a namespace associated with it, describing the operation creating the relationship.

For instance an image that was created using delta vision deconvolution algorithm should look like:

Derive [image A, image B] ns:/ANALYSIS/DELTAVISION/DECONVOLUTION

This will require the creation of 3 tables:
imageImageLink
roiImageLink
roiRoiLink

Change History (2)

comment:1 Changed 14 years ago by jburel

duplicated, merged ticket#1741 and ticket#1650

comment:2 Changed 14 years ago by jburel

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.63673 sec.)

We're Hiring!