Project

General

Profile

Actions

bug #10132

closed

Coding of special characters in Vaadin/PhycoBank (in docker instance only)

Added by Wolf-Henning Kusber over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Highest
Assignee:
Category:
server-maintenance
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Found in Version:
Tags:

Description

Copy a special character from a PDF, a MS Word file. Input of a special character by a user, using the keybord of a computer should work without problems.

State of the art 29 Aug 2022:

Special characters checked ö and è from PDF -> Vaadin/Portal ?
Can be correted in Vaadin by typing in ö or è but is saved in Vaadin and shown in Portal as ?
Can be correted in Vaadin by copying ö or è from a Word document, but is saved in Vaadin and shown in Portal as ?
This is critical:
Example:
è
PDF from URL https://fottea.czechphycology.cz/corproof.php?tartkey=fot-000000-0420
Production PhycoBank http://phycobank.org/103314

ö: http://phycobank.org/103313

Copy [long -(halbgeviertstrich?)] from PDF -> Vaadin/Portal ?
Can be corrected by typing in a Minus -

Copy " from PDF -> Vaadin/Portal ?
Can be corrected typing in a "

Old entries are OK, see e.g. http://phycobank.org/100991

Actions #1

Updated by Andreas Müller over 1 year ago

  • Category changed from cdm-vaadin to server-maintenance
  • Status changed from New to In Progress
  • Priority changed from New to Highest
  • Target version changed from Unassigned CDM tickets to Release 5.33

The problem seems to occur only when using the docker installation. When running the CDM Server on the default BGBM instance it does not occur.

Actions #2

Updated by Andreas Müller over 1 year ago

Helpfull Queries:

SELECT *
FROM SpecimenOrObservationBase osb
WHERE osb.titleCache LIKE 'Mon%';

SELECT *
FROM GatheringEvent ge
WHERE ge.id = 2495;

SELECT *
FROM LanguageString ls
WHERE TEXT LIKE '%%'
ORDER BY id DESC; 


SELECT *
FROM LanguageString_AUD ls
ORDER BY id DESC; 
Actions #3

Updated by Andreas Müller over 1 year ago

Only fields mapped as @Lob seem to have the problem (e.g. Reference.title but not Reference.abbrevTitle)

Actions #4

Updated by Andreas Müller over 1 year ago

  • Subject changed from Coding of special characters in Vaadin/PhycoBank to Coding of special characters in Vaadin/PhycoBank (in docker instance only)
  • % Done changed from 0 to 10
Actions #5

Updated by Katja Luther over 1 year ago

Setting the encoding of the docker instance does not make any change ...

Actions #6

Updated by Katja Luther over 1 year ago

using new cdmServer (5.33.0) and test db for some more tests. -> does not make any difference.

Actions #7

Updated by Katja Luther over 1 year ago

I tested a fresh docker installation in my VM and with this instance it does not make any problems, so I would uninstall docker during the release and reinstall it on production. Hopefully this would solve this issue.

Actions #8

Updated by Andreas Müller over 1 year ago

  • Status changed from In Progress to Feedback

Katja Luther wrote in #note-7:

I tested a fresh docker installation in my VM and with this instance it does not make any problems, so I would uninstall docker during the release and reinstall it on production. Hopefully this would solve this issue.

Good news that it works on your machine.
Question: shouldn't we try this before the release already.
Reasons:

  • if we need further adaptations that need a release we should know this before the release.
  • we should try to fix this as soon as possible
  • maybe not necessary to stop other cdmserver instances for reinstalling docker so no real interruption (except for phycobank dataportal)
Actions #9

Updated by Katja Luther over 1 year ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Katja Luther to Wolf-Henning Kusber
  • % Done changed from 10 to 60

Please review

Actions #10

Updated by Wolf-Henning Kusber over 1 year ago

  • Assignee changed from Wolf-Henning Kusber to Katja Luther
  • % Done changed from 60 to 100

coding now correct. Ticket can be closed.

Actions #11

Updated by Wolf-Henning Kusber over 1 year ago

Habe auch ein Sonderzeichen eingegeben, gespeichert und es wurde korrekt angezeigt (bei einem nicht publizierten Record)

Actions #12

Updated by Katja Luther over 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF