EDIT

Problems with current implementation of the new webservice:

1. relations.representation_L10n and relations.representation_L10n_abbreviatedLabel is always an empty string
2. The TaggedText lists in the misapplications field of the DTO need the relation ship type as additional information: "Im Portal können ALLE TaxonRelationen ein und ausgeschaltet werden, so auch die MAs und INVALID_DESIGNATION_FORs. Daher muss ich die misapplications im DTO unterscheiden können . Ein einfaches Feld misapplications mit einer Liste von TaggedTitle reicht nicht aus. Der Relationstype fehlt hier." --> use an DTO class which has two fields, taggedText and relationshiptype

A disadvantage of the current implememtation of the taxon relationships webservice and DTO when being used in the dataportal:

The secRefs are returned in the taggedText of the DTO only as authorship - good! The dataportal needs to show the full citation of the secRef in as footnote. The fullCitation is not included in the DTO, so the dataportal would need to fetch the reference from the webservice. Therefore I suggest to add the reference titlecache as label to the typedEntityReference:

{

    "entityReference": {
        "label": ">>>>>TITLE_CACHE<<<<<",
        "type": "Reference",
        "class": "TypedEntityReference",
        "uuid": "206add8c-3eae-4d9c-872c-e15409d2a3d9"
    },
    "text": "Cheek, Jebb 2001",
    "type": "secReference",
    "class": "TaggedText"

},

Ok from this future perspective it makes sense to decouple the loading of the references and the display of the MANs. Extending the ReationshipDTO could be an alternative but bloating the tagged text list to transport the full source information makes not much sense.
As the full reference information will be displayed in the footnotes we could do bulk loading of all references/sources when processing this page part. By this we can limit the overhead imposed by the required additional requests.

When implementing:

add NARROW NO-BREAK (\u202F) after doubtful marker as requested in #5492

can you please add the marker to the class UTF8 in cdmlib commons?

should we change Assignee of this ticket?

Andreas Müller wrote:

should we change Assignee of this ticket?

No need to, the NARROW_NO_BREAK is now a constant in the UTF8 class.

But what about the

String doubtfulRelationStr = taxonRelationship.isDoubtful() ? "?" : "";

do we also need to append the NARROW_NO_BREAK to the doubtful relation marker?

Andreas Kohlbecker wrote:

the NARROW_NO_BREAK is now a constant in the UTF8 class.

But what about the

String doubtfulRelationStr = taxonRelationship.isDoubtful() ? "?" : "";

do we also need to append the NARROW_NO_BREAK to the doubtful relation marker?

Yes I think we should handle them both similar.

By the way, probably you have realized, that the handling of the doubtful marker is not very implemented yet. One time it is part of Tag type "symbol" one time it is part of "separator" which is not really correct. There might be better ways. E.g. we could have "doubtful" as a separate Tag type instead. And then use NARROW_NO_BREAK as post-separator. Needs to be discussed.