Skip to content
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

Add genus, specificEpithet and infraspecificEpithet #61

Open
peterdesmet opened this issue Feb 13, 2018 · 5 comments
Open

Add genus, specificEpithet and infraspecificEpithet #61

peterdesmet opened this issue Feb 13, 2018 · 5 comments
Assignees
Milestone

Comments

@peterdesmet
Copy link
Member

Could be generated from the scientificName with the GBIF name parser. We could then choose one of the following approaches:

Add as 3 columns to source file

Bulk of it could be populated once with GBIF name parser and then maintained manually.

Main advantage: speed + control

Add as 3 columns in mapping

Would have to be parsed every time (slowing down the publication)

Main advantage: no maintenance

@peterdesmet
Copy link
Member Author

@qgroom
Copy link
Collaborator

qgroom commented Feb 13, 2018

Could the parser be called as part of the script, or does this mean adding a step?

@peterdesmet
Copy link
Member Author

It could be called as part of the script

@LienReyserhove LienReyserhove added this to the v1.5 milestone Mar 7, 2018
@LienReyserhove
Copy link
Contributor

It would be good to have an answer on this question in the meantime: (see #23)

Chenopodium album L. x hircinum can be interpreted as:

  • A named subspecies hybrid of Chenopodium album>
  • A hybrid formula: Chenopodium album L. x Chenopodium hircinum L.
    If the latter, I would spell out the name in full. It's best to do this for all hybrid formulas.

@peterdesmet
Copy link
Member Author

Agreed. Name should either be:

  • Chenopodium album L. subsp. x hircinum
  • Chenopodium album L. x Chenopodium hircinum

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

No branches or pull requests

3 participants