Project

General

Profile

Bug #4855

Reorder the Full Annotation rows to match madlib order

Added by ben leinfelder over 10 years ago. Updated over 6 years ago.

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

0%

Estimated time:
Bugzilla-Id:
4855

Description

From Shawn:
---
2. The full annotation should be more closely aligned to the terms
used in the madlib. So, e.g., It should go in this order:

Characteristic
Entity
Standard
Protocol
Context

3. This would mean we use a different identifier than ox -- maybe just
a number (and drop the o part, or Entity1, Entity2, etc.)

History

#1 Updated by ben leinfelder about 10 years ago

I think this makes the table even more confusing than it already is.

The current order matches the examples laid out during SEEK development.

Maybe Context should not even appear here. Or maybe I need to start implementing that connected-line-style mockup we came up with.

Are people even using the table to directly edit the annotations?

#2 Updated by Margaret O'Brien about 10 years ago

(In reply to comment #1)

I think this makes the table even more confusing than it already is.

The current order matches the examples laid out during SEEK development.

Maybe Context should not even appear here. Or maybe I need to start
implementing that connected-line-style mockup we came up with.

Are people even using the table to directly edit the annotations?

I frequently use the table -- it is especially useful when I want to see how I annotated the columns nearby

#3 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 4855

#4 Updated by ben leinfelder over 6 years ago

  • Target version changed from Unspecified to morpho-plugin-0.9.0

Also available in: Atom PDF