Skip to content

Instantly share code, notes, and snippets.

@timrobertson100
Last active August 29, 2019 11:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save timrobertson100/7d9bd922eb5c9b2a561f234829e87977 to your computer and use it in GitHub Desktop.
Save timrobertson100/7d9bd922eb5c9b2a561f234829e87977 to your computer and use it in GitHub Desktop.
occurrenceCount,
// verbatim fields in records
v_kingdom,
v_phylum,
v_class,
v_order,
v_family,
v_genus,
v_scientificName,
v_taxonRank,
v_verbatimTaxonRank,
v_specificEpithet,
v_infraSpecificEpithet,
v_scientificNameAuthorship,
// existing classification (i.e. what is in production)
kingdom,
phylum,
class,
order,
family,
genus,
species,
scientificName,
acceptedScientificName,
status
kingdomId,
phylumId,
classId,
orderId,
familyId,
genusId,
speciesId,
taxonId,
acceptedTaxonId,
// new versions
new_kingdom,
new_phylum,
new_class,
new_order,
new_family,
new_genus,
new_species,
new_scientificName,
new_acceptedScientificName,
new_status
new_kingdomId,
new_phylumId,
new_classId,
new_orderId,
new_familyId,
new_genusId,
new_speciesId,
new_taxonId,
new_acceptedTaxonId
@mdoering
Copy link

Suggestions:

  • nubID -> taxonId
  • add status (accepted, syn, etc) to both old and new
  • add acceptedName to both in case of synonyms

@mdoering
Copy link

a default sorting by scientificName or new_scientificName should be good

@timrobertson100
Copy link
Author

Thanks. Sorting would happen post production using e.g. linux sort
The rest look good

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