5,887
edits
Data Ingestion Guidance: Difference between revisions
→Using PhyloCode Nomenclature
| Line 148: | Line 148: | ||
Anyone considering contributing data should read these [[Data_Problems |anecdotes]]. They come from users of iDigBio's aggregated data, and reveal issues of data quality. | Anyone considering contributing data should read these [[Data_Problems |anecdotes]]. They come from users of iDigBio's aggregated data, and reveal issues of data quality. | ||
==Using PhyloCode Nomenclature== | ===Using PhyloCode Nomenclature=== | ||
If you are using PhyloCode nomenclature the following fields are recommended, instead of the standard Linneaen hierarchy-based fields (i.e., family, genus, specificEpithet): <br> | If you are using PhyloCode nomenclature the following fields are recommended, instead of the standard Linneaen hierarchy-based fields (i.e., family, genus, specificEpithet): <br> | ||
*higherClassification: for the PhyloCode clades | *higherClassification: for the PhyloCode clades, a string of names separated by commas can be entered. | ||
*taxonRemarks: to explain that you are not using Linneaen classification (http://rs.tdwg.org/dwc/terms/index.htm#taxonRemarks) | *taxonRemarks: to explain that you are not using Linneaen classification (http://rs.tdwg.org/dwc/terms/index.htm#taxonRemarks) | ||