NOTE: THE INFO BELOW HAS BEEN *SUPERCEDED* BY NEW PROCEDURES. PLEASE CONTACT email@example.com TO GET INFO RE: NEW STANDARDS & PROCEDURES (pt/04APR2002).
The Monitoring Database taxon codes are STANDARD among many organizations; please DO NOT indiscriminately add them; YOU SHOULD *NEVER* CHANGE THEM.
You MAY, however, add codes for taxa with the 'loc.' rank. When doing so, PLEASE incorporate your organization's 1-character code (e.g. Nature Conservancy's is 'N', thus 'Cyanea sp. loc. Waikamoi T5P3 02/10/96' would be 'CyaSp.N01'). (The number after the organization code is arbitrary [suggestion: sequential]; its only purpose is to allow for creation of unique taxon codes.) Note that if this scheme is followed, "personal" codes that you send to/receive from others will NEVER conflict!
Current organization code information is available in the dBase table named "TCORGCOD.DBF" contained in the online zip file DBFs4web.zip . If you are using the Monitoring Database, you should already have an organization code. If you are using the Monitoring Database and DON'T have [or don't know] your organization's code, or if plan to use these standard Taxon Codes to exchange data with others in the state of Hawaii, please contact the Monitoring Database System Coordinator to get a code for your organization.
Taxon codes comprise the first three letters of the Genus* + first three letters of the Species* + first three letters of the Infraspecific epithet* (see table structure information for the TAXA.DB table). If this scheme produces duplicates, three additional digits are added, giving each a unique number based on ALPHABETICAL ORDER of the taxa (Genus* + Species* + Infraspecific epithet*) which would otherwise be duplicates. Leave several numbers (typically 10) between new additions to allow for future infra-alphabetical entries. (*All nomenclature is either based on Bishop Museum standard taxonomy, or "alt." nomenclature.) NOTE THAT ONLY THE MONITORING DATABASE SYSTEM ADMINISTRATOR--NOT YOUR SITE'S DATABASE ADMINISTRATOR--MAKES THESE CHANGES!! Your site's Database Administrator will be notified of official changes via the HIMONDBA-L list. If you think something needs to be changed, have your site's Database Administrator contact the Monitoring Database System Coordinator.
For example, by the primary rule, Cyrtandra grayana and Cyrtandra grayi would be assigned 'CyrGra', creating a duplication conflict. Therefore, they are assigned CyrGra010 and CyrGra020, respectively. Since Cyrtandra grayana comes first alphabetically, it gets the lower number. Ten (10) numbers are skipped in between to allow for the possibility of a new taxon, e.g. Cyrtandra grayensia, which would be CyrGra015.
Remember that ANY CHANGES to species names or Taxon Codes (including "loc." taxa) should be made ONLY by your organization's Database Administrator!
Also remember, it is the responsiblity of the data quality control manager of your organization (typically the Site Manager) to ensure that codes are entered correctly.
Refer to the Monitoring Database documentation for further information.