Project

General

Profile

Actions

bug #6380

closed

typedesignations missing in homotypic group

Added by Andreas Kohlbecker about 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Highest
Category:
cdm-dataportal
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Found in Version:

Description

This issue seems to occur only in special cases but point out a general problem with the way the typedesignations are collected for a homotypic group.
This problem may also account to heterotypic groups.
In the homotypic group of Youngia atripappa (http://cichorieae.e-taxonomy.net/portal/cdm_dataportal/taxon/a67fc2ab-1452-4c32-84b6-8953111af9d6/synonymy) typedesignations are distributed between several names:

  • Youngia atripappa : 1 isolectotype
  • Crepis gracilis: 1 Lectotype
  • Crepis atripappa: 1 isolectotype
  • Youngia gracilis: 1 isolectotype
  • Youngia stebbinsiana: 1 isolectotype

In the portal code the typedesignatinons for the accepted taxon name and for the first name in the homotypic group after the accepted are explicitly retrieved from the portal/name/{uuid}/typeDesignations webservice.
The service and dao methods behind this service only return the typedesignations associated with the given name and are missing all others.
A solution would be to use the existing eu.etaxonomy.cdm.persistence.dao.name.IHomotypicalGroupDao.getTypeDesignations() method. For this the HomotypicalGroup uuid must be present in the portal.

TODO

  • check if this problem also accounts to heterotypic groups
  • Fix incomplete typedesignatinons retrieval

Related issues

Related to EDIT - feature request #7696: use compact type representations in the synonymy as provided by the typedesignations/byTaxon/{taxon_uuid} serviceResolvedAndreas Müller

Actions
Copied to EDIT - feature request #8390: implement /portal/name/{uuuid}/typeDesignationsInHomotypicalGroup ClosedAndreas Kohlbecker

Actions
Actions

Also available in: Atom PDF