Context Navigation

← Previous Ticket
Next Ticket →

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 #2821 (closed)

Opened 10 years ago

Closed 8 years ago

Model synchronisation, unification & evolution

Reported by:	cxallan	Owned by:
Priority:	major	Milestone:	Unscheduled
Component:	Specification	Keywords:	n.a.
Cc:	jburel, ajpatterson, jamoore	Story Points:	n.a.
Sprint:	n.a.	Importance:	n.a.
Total Remaining Time:	0.0d	Estimated Remaining Time:	n.a.

Description

There are many cases where the OME-XML model differs from the OMERO model. This overarching story should be used to gather all of these inconsistencies for review and subsequent resolution or documentation as to the reason for the difference.

References

Referenced by:

← Requirement (#6299): OME Data Model Development ← Requirement (#7836): Model-Database alignment
References:
→ Task (#2822): Well is missing status field → Task (#5112): Remove OTF from the Model/Schema ( Owner: ajpatterson Keywords: schema, nextrelease ) → Task (#2824): OTF: objective vs objective settings ( Owner: ajpatterson Remaining Time: 0 ) → Task (#2831): OTF: Path ( Owner: ajpatterson ) → Task (#2826): Microbeam manipulation ( Owner: ajpatterson Remaining Time: 0 )

Change History (4)

comment:1 Changed 9 years ago by ajpatterson

Summary changed from Model synchronization and unification to Model synchronisation, unification & evolution

comment:2 Changed 9 years ago by ajpatterson

Component changed from Model to Specification

comment:3 Changed 8 years ago by agilo

Status changed from new to accepted

Updated status, related task in progress

comment:4 Changed 8 years ago by jburel

Resolution set to fixed
Status changed from accepted to closed

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

Download in other formats: