Actions
bug #7766
closedRemaining issues for using relationship DTO webservice in portal
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-dataportal
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
for details see #7658
- taxonrelation footnotes missing (see #7658#note-51 for details)
- sort order of the relations (see #7658#note-46 for details) The expected sort order is:
- pro parte/partial synonyms,
- then invalid designations,
- then MANs
- followed (or including?) pro parte/partial MAN
- and finally concept relationships.
- links to related taxa (new) - before the refactoring the related concepts were linked, at least for real concept relationships we should again do this, needs discussion if we also want this for ppSyns, MANs, and inval desigs. (maybe configurable?)
- related issue for formatting MAN search results: #7771
- identifier links missing when footnote is created in MANs code part: #7778
Related issues
Updated by Andreas Kohlbecker over 4 years ago
- Copied from feature request #7658: use new taxon relationship DTO webservice in portal added
Updated by Andreas Müller over 4 years ago
- Subject changed from taxonrelation footnotes missing after using relationship DTO webservice in portal to Remaining issues for using relationship DTO webservice in portal
- Description updated (diff)
Updated by Andreas Müller over 4 years ago
- Related to feature request #7771: Format Misapplication search results as MAN, not as accepted taxa added
Updated by Andreas Kohlbecker over 4 years ago
- Copied to bug #7778: identifier links missing in taxon relations footnotes added
Updated by Andreas Kohlbecker over 4 years ago
- Status changed from Feedback to Closed
this issue seems complete, since #7771 is in it's own ticket.
Updated by Andreas Müller over 4 years ago
- Status changed from Closed to Resolved
- Assignee changed from Andreas Kohlbecker to Andreas Müller
- % Done changed from 0 to 90
Updated by Andreas Kohlbecker over 3 years ago
- Status changed from Resolved to In Progress
- Assignee changed from Andreas Müller to Andreas Kohlbecker
- % Done changed from 90 to 70
The sort order seem to have problems. Is this an regression or has this point be missed?
Updated by Andreas Kohlbecker over 3 years ago
- Target version changed from Release 5.4 to Release 5.11
Updated by Andreas Kohlbecker over 3 years ago
- Target version changed from Release 5.11 to Release 5.12
Updated by Andreas Kohlbecker about 3 years ago
- Target version changed from Release 5.12 to Release 5.13
Updated by Andreas Kohlbecker almost 3 years ago
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
Andreas Kohlbecker wrote:
The sort order seem to have problems. Is this an regression or has this point be missed?
The sort order is fixed now. The correctness is approved by the test which has been adapted to meet the requirements from the ticket description.
Actions