task #10222
Updated by Andreas Müller about 1 year ago
... to improve performance and simplify dataportal rendering. If possible formatting should take place server side.
Open issues: how to pass configuration?
* huge number of parameters
* json configuration
Discussion about data, contained in DTO(s):
* taxonName: should everything be handled in typedLabel or in own DTO?
* if we have an own dto, we can add rank and rankorder index, but maybe we only need the rank string if all ordering is done serverside
* name relationships
* specimen: could we reuse or reorganize the already existing derivedUnit/fieldunit dtos? They are already implemented for the use in dataportal
* there are already methods implemented to get the specimen subtree for one taxon to get the data for the specimen tree view, they already return dtos (OccurrenceController.doGetRootUnitDTOs() and this calls OccurenceServiceImpl.findRootUnitDTOs)
* currently actually the facts are merged into the feature tree (see _mergeFeatureTreeDescriptions in cdm_api.module of the dataportal code), we should handle this similar when creating the dto
* ~~the distribution facts are handled separately in dataportal, maybe we should handle them in a separate item in the dto as well.~~