Project

General

Profile

feature request #8850

Show annotations for DerivedUnits (Fieldunits etc) in Registration and other pages

Added by Andreas Kohlbecker 8 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Highest
Category:
cdm-dataportal
Target version:
Start date:
02/19/2020
Due date:
% Done:

100%

Severity:
normal
Tags:

Description

Example:

In Vaadin habe ich einen vorläufigen Kommentar, der als Note an der mit Pfeil angegebenen Stelle ausgegeben werden könnte:

Die Information ist formal ausreichend. Der Kommentar gibt aber wesentliche Zusatzinformationen für Nutzende. In diesem Fall ist aus formalen Gründen ein Specimen in TNS hinterlegt worden. Tatsächlich wichtig ist aber, dass mit dem Stamm SAG 19.88 gearbeitet worden. Wir hatten vereinbart, dass ich die Note einer Kategorie für die Veröffentlichung zuweise, welche war das? M.E. ist die tatsächliche Publikation der Notes noch nicht implementiert.

Über diese Struktur könnten wir auch einen mehrfach von mir gewünschtes Feature lösen, das in der Implementierung problematisch wäre.

Sowas wie „The holotype is represented by Fig. 2”. Das bekommen wir in der gegenwärtigen Struktur nicht atomisiert unter, als Kommentar wäre das völlig ausreichend.

Aktueller Anlass meiner Mail war, dass ich der Kuratorin der SAG den oben angegebenen Record schickte, um sie darauf aufmerksam zu machen, dass ihre SAG-Datenbank eine falsche Georeferenzierung des Strains SAG 19.88 hat. Der Bezug fehlt aber zurzeit bei uns noch, da er nicht unmittelbar für die Registrierung notwendig ist.

picture911-1.png View (11.6 KB) Andreas Kohlbecker, 02/19/2020 11:21 AM

picture291-1.png View (209 KB) Andreas Kohlbecker, 07/23/2020 02:19 PM

picture166-1.png View (37.1 KB) Wolf-Henning Kusber, 08/19/2020 05:20 PM

picture166-2.png View (46.1 KB) Wolf-Henning Kusber, 08/19/2020 05:20 PM

picture220-1.png View (53.3 KB) Andreas Kohlbecker, 08/19/2020 07:20 PM

Associated revisions

Revision 0e617798 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 showing fieldunit annotations in registration page

Revision c558bf25 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 adding entity refernces to DerivedUnitFacade for detivedUnit and fieldUnit

Revision 991ae630 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 annotations for FieldUnits and nameTypeDesignations in registration and name page

Revision c47414aa (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 test for footnotes in registration and name pages; footnote support in BaseElement

Revision 26f042e4 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 fixing uninitialized variables

Revision 73302d89 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 adapting tests to new annotation footnotes

Revision d7d89e58 (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 cdm_compose_annotations_uri() handling cases withiut fieldUnit

Revision 0eb48f9b (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8850 cdm_compose_annotations_uri() handling cases withiut fieldUnit - comment

History

#1 Updated by Andreas Kohlbecker 8 months ago

  • Status changed from New to Rejected

#2 Updated by Andreas Kohlbecker 8 months ago

  • File picture911-1.png View added
  • Subject changed from Extend collection editor by additional fileds for townOrLocation, codeStandard to Show annotations for DerivedUnits (Fieldunits etc) in Registration and other pages
  • Category changed from cdm-vaadin to cdm-dataportal
  • Status changed from Rejected to New

#3 Updated by Andreas Kohlbecker 8 months ago

  • Description updated (diff)

#4 Updated by Wolf-Henning Kusber 8 months ago

Example with editorial annotation and etymology annotation: http://phycobank.org/102135

#5 Updated by Andreas Kohlbecker 7 months ago

  • Target version changed from Release 5.13 to Release 5.14

#6 Updated by Andreas Müller 6 months ago

  • Target version changed from Release 5.14 to Release 5.15

#7 Updated by Andreas Müller 4 months ago

  • Target version changed from Release 5.15 to Release 5.18

#8 Updated by Andreas Kohlbecker 3 months ago

#9 Updated by Andreas Kohlbecker 3 months ago

  • Status changed from New to Resolved
  • Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
  • % Done changed from 0 to 50

this is solved completely. In contrast the original suggestion, I put the footnote into the registration block, since other footnotes are also located there.

Please review

#10 Updated by Wolf-Henning Kusber 2 months ago

  • File picture166-1.png View added
  • File picture166-2.png View added
  • Status changed from Resolved to Feedback
  • Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
  • % Done changed from 50 to 60

Interesting solution. There is something resolved.

But how can you decide if the note is related to the field unit or the specimen?
In fact, I did not differentiate, and the current note should be related to the specimen and has nothing to do with the field unit.

In the Test portal this is confusing:
On the registration page: no note,
Clicking on the specimen link, I come to the page called "Specimen Details": no note (I would expect this here)

On the bottom of the page there is a link to field unit (I would not click there... but if I do so, I come to another Page called "Specimen Details" with the note.

This is rather confusing...
I cannot recommend this solution for the production as is.

#11 Updated by Andreas Kohlbecker 2 months ago

The test portal was connected to the production server. This is the reason why the note was not visible. When connecting the portal to the test server the reult is as expected:

#12 Updated by Andreas Kohlbecker 2 months ago

  • Status changed from Feedback to Closed
  • % Done changed from 60 to 100

I am now closing this ticked as it is apparantly being solved

#13 Updated by Andreas Müller 2 months ago

  • Target version changed from Release 5.18 to Release 5.17

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)