Skip to content

Ability to nest synonymised name under new name in trees #3011

@grantfitzsimmons

Description

@grantfitzsimmons

Currently, Specify indicates a synonym by colouring its name red in the tree. However, it is retained in its original place in the taxon tree. Some of our collections require the synonymised names to be nested under the new name. Particularly in the insect collection, there can be many synonyms attached to a ‘current’ taxon and the current way Specify displays this data in the tree is not ideal.

It would be good if an option to switch to a nested view of synonyms could be implemented.
 
Also, I believe that currently when you synonymise taxa all records will be ‘moved’ to the new name, with the old node in the taxon tree displaying a ‘0’ count. Which means that any deprecated names cannot retain attached specimens, is this correct?
If so, this creates a bit of an issue for the insect collection as a lot of their synonym names have type records attached to them. Do you have any suggestions on how to handle this scenario?

Attached a couple of screenshots from the current insect collection system to help illustrate the complexity:

A)     Example of synonymy at the genus level (synonym genera)

image

B)     Example of synonym genera and synonym species (displaying species that were originally described in other genus with mention to subgenus and species.

image

C)     In the case of a new combination, here is an example of a species (not a synonym) displayed how it was originally described under the current combination

image

D)     In incertae sedis, species from genera present elsewhere in the tree (genus Formica)

image

Requested By: Corinna P at CSIRO (Asana)

Metadata

Metadata

Assignees

No one assigned

    Labels

    1 - RequestA request made by a member of the community2 - TreesIssues that are related to the tree system and related functionalities.

    Type

    No type

    Projects

    Status

    ✅ Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions