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"

Task #2824 (closed)

Opened 10 years ago

Closed 9 years ago

OTF: objective vs objective settings

Reported by: jburel Owned by: ajpatterson
Priority: minor Milestone: OMERO-Beta4.3
Component: General Version: n.a.
Keywords: n.a. Cc: jamoore, cxallan
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: n.a.

Description (last modified by jburel)

An XML OTF expects an objective settings, and OMERO OTF expects an objective.


Decision

OTF should probably be removed from the schema, otherwise we will have to model other functions e.g. IRF used in FLIM
In FLIM case, a file annotation is used.
If not removed, ask Jason and/or Sam to clarify

Change History (3)

comment:1 Changed 9 years ago by jburel

  • Description modified (diff)
  • Milestone changed from Unscheduled to OMERO-Beta4.3

comment:2 Changed 9 years ago by cxallan

  • Cc ajpatterson removed
  • Owner set to ajpatterson

comment:3 Changed 9 years ago by Andrew J Patterson <ajpatterson@…>

  • Remaining Time set to 0
  • Resolution set to fixed
  • Status changed from new to closed

(In [39f176163a118623fdf9f45f448699d681fbf443/ome.git] on branch develop) Deprecate OTF (close #2824) (see #2831)

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.77054 sec.)

We're Hiring!