New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we add lots of vernacular names to the synonyms list #160

Open
mtholder opened this Issue Sep 21, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@mtholder
Member

mtholder commented Sep 21, 2015

Pros:

  • would make tree browsing much easier

Cons:

  • internationalzation
  • lots of new synonyms (probably not a big deal for smasher or taxomachine)
  • some vernacular names are homonyms for lots taxa that are not closely related (e.g. "robin")

See https://groups.google.com/forum/?fromgroups&hl=en#!topic/opentreeoflife/4jDcxryXWxg

@jar398

This comment has been minimized.

Show comment
Hide comment
@jar398

jar398 Sep 21, 2015

Member

I think I asked around about this one a while ago, and decided to remove
them. I think many common names were mapping to a large number of different
species, and that was an annoyance during taxonomy synthesis. So the code
would probably have to tweaked to make them second-class synonyms (i.e. not
ones that would allow transitive synonymy across source taxonomies).

We have easy access to NCBI common names, e.g.
56350 | American kestrel | | common name |
100819 | common kestrel | | genbank common name |
148594 | lesser kestrel | | genbank common name |
1562128 | South African kestrel | | genbank common name |

On Mon, Sep 21, 2015 at 7:49 AM, Mark T. Holder notifications@github.com
wrote:

Pros:

  • would make tree browsing much easier Cons:
    • internationalzation
    • lots of new synonyms (probably not a big deal for smasher or
      taxomachine)
    • some vernacular names are homonyms for lots taxa that are not
      closely related (e.g. "robin")

See
https://groups.google.com/forum/?fromgroups&hl=en#!topic/opentreeoflife/4jDcxryXWxg


Reply to this email directly or view it on GitHub
#160.

Member

jar398 commented Sep 21, 2015

I think I asked around about this one a while ago, and decided to remove
them. I think many common names were mapping to a large number of different
species, and that was an annoyance during taxonomy synthesis. So the code
would probably have to tweaked to make them second-class synonyms (i.e. not
ones that would allow transitive synonymy across source taxonomies).

We have easy access to NCBI common names, e.g.
56350 | American kestrel | | common name |
100819 | common kestrel | | genbank common name |
148594 | lesser kestrel | | genbank common name |
1562128 | South African kestrel | | genbank common name |

On Mon, Sep 21, 2015 at 7:49 AM, Mark T. Holder notifications@github.com
wrote:

Pros:

  • would make tree browsing much easier Cons:
    • internationalzation
    • lots of new synonyms (probably not a big deal for smasher or
      taxomachine)
    • some vernacular names are homonyms for lots taxa that are not
      closely related (e.g. "robin")

See
https://groups.google.com/forum/?fromgroups&hl=en#!topic/opentreeoflife/4jDcxryXWxg


Reply to this email directly or view it on GitHub
#160.

@jar398

This comment has been minimized.

Show comment
Hide comment
@jar398

jar398 Oct 24, 2015

Member

I don't know what next steps are for this issue, so I'm going to assign it to Mark and flag it 'needs discussion'.

Member

jar398 commented Oct 24, 2015

I don't know what next steps are for this issue, so I'm going to assign it to Mark and flag it 'needs discussion'.

@josephwb

This comment has been minimized.

Show comment
Hide comment
@josephwb

josephwb Oct 5, 2016

Member

i added a hesitant thumbs-up. it might be useful in the tree viewer (e.g. educational purposes) and perhaps sometimes curating trees (i've run across this once or twice), but i understand the cons.

Member

josephwb commented Oct 5, 2016

i added a hesitant thumbs-up. it might be useful in the tree viewer (e.g. educational purposes) and perhaps sometimes curating trees (i've run across this once or twice), but i understand the cons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment