2 extra properties: Nucleus IsOpaque & Edge IsOpaque

[wimallegaert]

For herring, the distinction between autumn/winter spawners and spring spawners is done based on the structure of the nucleus (opaque or translucent). We would like to ask for an additional data field to be able to fill in this observation. That would be an extra field in the screen that pops up after the annotation is completed. A non-obligatory field because it is only relevant for herring.

Suggested by Loes Bolle

2 extra properties (boolean) per annotation needed:

• Nucleus IsOpaque
• Edge IsOpaque

[wimallegaert]

• Add 2 extra non-obligatory annotation properties: OtolithNucleusState and OtolithEdgeState
• The properties can have 3 different values: Opaque (O), Translucent (T) or NULL
• Integrate new properties in the annotation grid & annotation popup
• Integrate new properties in data transfer object annotation
• Integrate new properties in methods GetFileWithSampleAndAnnotations, AddAnnotation, UpdateAnnotations

Estimation implementation effort ILVO: 8h

WMR suggested alternative implementation: develop functionality so that properties can be added dynamically to an annotation via the Web API. This solution will be for sure more future proof, in this case new future annotation properties could be added without changes to the software. Unfortunately this development is more complex.

[wimallegaert]

The following was agreed on WGSMART Meeting April 25th:

• the properties OtolithNucleusState and OtolithEdgeState will be integrated in SmartDots as fixed properties;
• their will be an option in a WebAPI method available to show or hide the new properties in SmartDots. The show/hide property can be set per activity

The options Opaque and Translucent for the NucleusState and the EdgeState will be displayed in a dropdown list / combo box control. This seems clearer to us than a checkbox.

[kevinatilvo]

It is now possible to let the software show 2 additional columns (Nucleus and Edge) in the Annotation panel. Extra functionality was added to the Web API to show or hide these properties per event. In the demo- environment the extra properties are shown in the Herring workshop (20170009).

In the annotation grid, the 2 extra columns are shown. You can manage the Edge and Nucleus properties directly in the grid. The available options for both properties are: Opaque, Translucent, NA (not applicable). The software will translate NA to null (nothing).

The Edge and Nucleus fields are also integrated in the popup window to edit/save the annotation.

[cmspinto]

when activating this extra properties they always go together or they should be activated separately?

So I guess that what I’m asking is if we do this:

1st scenario:

Enable Nucleolus property?

Enable Edge property?

2nd scenario:

Enable Nucleolus and Edge properties?

This option will be in the edit event page.

[cmspinto]

We go for the 1st scenario, Loes confirmed this in an email from the 9th of September.