DB Manager :: Add obsolete species name
Introduction
This page will direct an xBio:D user on the procedures to follow in order to add a new obsolete species name, a common name, or another obsolete name at a different rank into the xBio:D database. Only users with taxonomic permissions and possess the taxonomic authority upon a certain group are able to manage taxonomies, so if you would like to contribute to the xBio:D taxonomic resources, please contact hol-help@osu.edu and request permission.
NOTE: Please understand the xBio:D Taxonomic Data Model before using any of the taxonomic features of the Database Manager.
Check for Existing Species
Before adding an obsolete combination to a species or taxon at any rank, it is necessary that the species concept already exist within the xBio:D database. All taxa are available through HOL, which will also list obsolete combinations for species, common names, as well as subjective synonomies of other species, and can easily be discovered via search. A species concept can have only one valid name associated with it and is considered the current combination. All other names that are also part of the concept are considered to be obsolete combinations. Any new species concepts added to the xBio:D database should also include the original combination (also known as a protonym or basionym), the species names used when first described and made available (see Wikipedia for basic definition of what an available name is). A common/vernacular name, although unavailable and unable to be considered valid according to nomenclatural codes, is also treated as an obsolete combination but is clearly marked as a common name in much the same way a misspelling of a species name is unavailable and never valid. If a species combination is not found, go to DB Manager :: Add new species or DB Manager :: Add subjectively synonymous species for directions on how to proceed. Only after a species concept has been confirmed to already exist should a new, obsolete species name be added.
Add Obsolete Species Name or Common Name in DB Manager
Go to the Add Taxon page of the DB Manager to begin. Since you are adding an obsolete combination to an existing species concept into the xBio:D database, make sure that the "Taxon Type" field is set to "Alternate name for existing concept" and the "Valid Flag" field is set to "Invalid". All other fields related to new concepts will be hidden once the taxon type is changed. In the "Parent Taxon Name" field, enter any of the names that are associated with the species concept.
The "Taxonomic Status" field should reflect the proper nomenclatural status for the name of the obsolete species combination or common name. In this part, only the zoological (ICZN) conventions for naming will be used, but other nomenclatural codes can also be applied here. If the obsolete combination is the species name as it was originally described, then the status should be "Original name/combination" and the "Author Name..." field would merely have the author's last name. If the obsolete combination is a species name that was subsequently moved into another genus, then the status would be "Subsequent name/combination" and the author would be the author's last name within parenthesis. In cases when a new name (nomen novum) is being entered, then the status should be "Replacement name" with the author's name without parenthesis. If a replacement name is subsequently moved into a different genus, then the name should be treated as any other subsequent combination.
When a junior homonym is entered as an obsolete combination, the status of the name should be "Junior homonym" for only the name as it was original described. Any other subsequent combination for the name should not have the "Taxonomic Status" field as a junior homonym.
Many names may not be "available" according to the ICZN code, and these names should be marked as such within their nomenclatural sttaus. If a misspelling of the specific epithet is present within an obsolete combination, then the status should be "Unavailable, literature misspelling". If a name is not accompanied by a sufficient description according to the code, the status for these names should be "Unavailable, nomen nudum". If a name was not made available by falling to meet any other requirement of the code, then the status for these names should be generically "Unavailable, other".
If a common name is desired to be added, change the "Taxonomic Status" field to "Common name" and leave the author field blank. Common names should maintain proper capitalization conventions according to the language for which the vernacular name is used.