bug #6380
Updated by Andreas Müller about 7 years ago
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. The 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