Project

General

Profile

feature request #9042

EnumTerm symbol and message in web service response

Added by Andreas Kohlbecker 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Priority14
Category:
cdmlib-remote
Target version:
Start date:
05/28/2020
Due date:
% Done:

0%

Severity:
normal

Description

Implementations of IEnumTerm may have a message in multiple languages and a symbol.

Implement a Json Bean processor to add these data to the web service responses.


Related issues

Related to Edit - feature request #9002: Find suitable symbols for excluded, unplaced, placement doubtful New 05/06/2020
Related to Edit - feature request #9010: Display taxon node status excluded, unplaced, placement doubtful on taxon page and taxon tree and show taxon node status note and taxon node source on taxon page Closed 05/13/2020
Related to Edit - feature request #9044: TaxonNodeDtoBeanProcessor supports new TaxonNodeStatus terms Closed 05/28/2020

Associated revisions

Revision 17d751c7 (diff)
Added by Andreas Kohlbecker 4 months ago

ref #9042 Helper class to provide localizations for EnumTerms + premliminar implementation of an EnumTermBeanProcessor

Revision fbbfd017 (diff)
Added by Andreas Kohlbecker 4 months ago

ref #9042 removing EnumTermBeanProcessor to avoid compilation problems

History

#1 Updated by Andreas Kohlbecker 4 months ago

  • Related to feature request #9002: Find suitable symbols for excluded, unplaced, placement doubtful added

#2 Updated by Andreas Müller 4 months ago

  • Subject changed from EumTerm symbol and message in web service response to EnumTerm symbol and message in web service response

#3 Updated by Andreas Kohlbecker 4 months ago

  • Related to feature request #9010: Display taxon node status excluded, unplaced, placement doubtful on taxon page and taxon tree and show taxon node status note and taxon node source on taxon page added

#4 Updated by Andreas Kohlbecker 4 months ago

#5 Updated by Andreas Kohlbecker 4 months ago

  • Priority changed from Highest to Priority14
  • Target version changed from Release 5.15 to cdm_dataportal - Next Major Release

ich überlege hin und her wie wir das am besten machen:

  1. Equivalent zu dem anderen Termen also als eigenes Objekt in JSON
  2. flach wie schon jetzt im TaxonNodeDtoBeanProcessor implementiert: #9044

Option 1. wäre mit dem Termen wie sie serialisiert werden konsistent, würde aber mit bestehendem code Probleme machen. Daher tendiere ich zu 2.

#6 Updated by Andreas Kohlbecker 4 months ago

[a.mueller]:

Modellseitig sollten die Enums sehr ähnlich wie Terme gehandelt werden (eigentlich sind es fixe Termvokabulare). Das spräche schon für 2.
Aber vielleicht machen wir das erst beim Umbau der remote API.

#7 Updated by Andreas Müller 4 months ago

  • Target version changed from cdm_dataportal - Next Major Release to Release 5.15

#8 Updated by Andreas Kohlbecker 3 months ago

  • Target version changed from Release 5.15 to Release 5.18

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)