Skip to content

Handling non-monophyly and search #975

@jrosindell

Description

@jrosindell

Problem - as phylogenetic data increasingly comes in it tends to break the monophyletic nature of well known named clades that people expect to be able to search for and find. In some cases it might be the phyloeny that's wrong and in other cases it will be a genuine reordering of things. Users expect to be able to type well known terms into search and find hits whether the things being searched for are non monophyletic or not. This probably demands some kind of solution in the medium term .... here are a few options

  1. Insert duplicate interior nodes for non monophyletic groups ____clade 1 and ____ clade 2 for instance.

  2. Save data on all taxonomic levels in the ordered leaves table so that search at least can find any of those things.

  3. Have tours on well known non monophyletic concerts (fish, reptiles etc.) that will come up in search.

  4. Maintain marked areas for well known non monophyletic groups (may not be easy to maintain - would need to be programmatic) - allow these to come up in search.

These are not mutually exclusive but I would guess that options 2 and 3 are the best to pursue first. 3 is already there and just needs more tours whilst 2 will enable better 'in house' dealing with the taxonomy and potential to make better species pages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions