Project

General

Profile

Actions
Copy link

feature request #9042

open

EnumTerm symbol and message in web service response

Added by Andreas Kohlbecker almost 3 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Priority14
Assignee:
Andreas Kohlbecker
Category:
cdmlib-remote
Target version:
Release 5.39
Start date:
Due date:
% Done:

0%

Estimated time:
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 doubtfulNewKatja Luther

Actions
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 pageClosedAndreas Kohlbecker

Actions
Related to EDIT - feature request #9044: TaxonNodeDtoBeanProcessor supports new TaxonNodeStatus terms ClosedAndreas Kohlbecker

Actions
Actions
Copy link
 #1

Updated by Andreas Kohlbecker almost 3 years ago

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

Updated by Andreas Müller almost 3 years ago

  • Subject changed from EumTerm symbol and message in web service response to EnumTerm symbol and message in web service response
Actions
Copy link
 #3

Updated by Andreas Kohlbecker almost 3 years 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
Actions
Copy link
 #4

Updated by Andreas Kohlbecker almost 3 years ago

Actions
Copy link
 #5

Updated by Andreas Kohlbecker almost 3 years 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.

Actions
Copy link
 #6

Updated by Andreas Kohlbecker almost 3 years 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.

Actions
Copy link
 #7

Updated by Andreas Müller almost 3 years ago

  • Target version changed from cdm_dataportal - Next Major Release to Release 5.15
Actions
Copy link
 #8

Updated by Andreas Kohlbecker over 2 years ago

  • Target version changed from Release 5.15 to Release 5.18
Actions
Copy link
 #9

Updated by Andreas Kohlbecker about 2 years ago

  • Target version changed from Release 5.18 to Release 5.19
Actions
Copy link
 #10

Updated by Andreas Kohlbecker about 2 years ago

  • Target version changed from Release 5.19 to Release 5.21
Actions
Copy link
 #11

Updated by Andreas Müller about 2 years ago

  • Target version changed from Release 5.21 to Release 5.22
Actions
Copy link
 #12

Updated by Andreas Kohlbecker almost 2 years ago

  • Target version changed from Release 5.22 to Release 5.39
Actions
Copy link

Also available in: Atom PDF