TaxonHistory

From Species File Help
(Difference between revisions)
Jump to: navigation, search
(formatting)
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''tblTaxonHistory''' contains history of concepts and nomenclature for protonyms added in version 4.0.
+
'''tblTaxonHistory''', history of concepts and nomenclature for protonyms. This is used only for taxa at genus rank or lower.
  
 
*TaxonHistoryID, integer, 4 bytes, primary key, identifier for taxon name and concept.
 
*TaxonHistoryID, integer, 4 bytes, primary key, identifier for taxon name and concept.
*TaxonNameID, integer, 4 bytes, = tblTaxon.TaxonNameID, identifier for the monomial name (protonym) associated with the history.
+
* [[Taxa|TaxonNameID]], integer, 4 bytes, = tblTaxon.TaxonNameID, identifier for the monomial name (protonym) associated with the history.
*SeqNum, integer, 2 bytes, sequence number within this TaxonNameID, 1-based values without gaps.
+
* FileID, integer, 4 bytes, = tblFiles.FileID, the species file the row is associated with. This column is being added in late 2013. Old rows with Status = 2 (artifact) remain with FileID = 0.
*NomenclatorID, integer, 4 bytes, = tblNomenclator.NomenclatorID, identifier for binomial name associated with the history.
+
* SeqNum, integer, 2 bytes, sequence number within this TaxonNameID, 1-based values without gaps.
*CiteRefID, integer, 4 bytes, = tblRefs.RefID, identifier for the reference that defined the nomenclatural or concept change.  May = 0 if change comes from other source explained in note or if the reference has not been identified.
+
* [[Nomenclator|NomenclatorID]], integer, 4 bytes, = tblNomenclator.NomenclatorID, identifier for binomial name associated with the history.
*NewNameStatus, integer, 1 byte, status of name when changed
+
* [[Refs|CiteRefID]], integer, 4 bytes, = tblRefs.RefID, identifier for the reference that defined the nomenclatural or concept change.  May = 0 if change comes from other source explained in note or if the reference has not been identified.
**0 = unspecified
+
* NewNameStatusID, integer, 4 bytes, status of name when changed
**1 = unchanged
+
** 0 = unspecified
**2 = new taxon name
+
** 1 = unchanged
**3 = made a synonym
+
** 2 = new taxon name
**4 = made valid or temporary
+
** 3 = made a synonym
**5 = new combination
+
** 4 = made valid or temporary
**6 = name deleted with no related name
+
** 5 = new combination
**7 = name deleted because of duplicate protonym, related name can be found in tblRelatedHistory
+
** 6 = name deleted with no related name
**8 = genus or species lowered to nominotypical sub
+
** 7 = name deleted because of duplicate protonym, related name can be found in tblRelatedHistory
**9 = nominotypical sub raised to genus or species
+
** 8 = genus or species lowered to nominotypical sub
**10 = name replaced by nominotypical sub
+
** 9 = nominotypical sub raised to genus or species
**11 = new nominotypical sub
+
** 10 = name replaced by nominotypical sub
*ConceptChange, integer, 1 byte, values in effect on completion of the change, permitted values:
+
** 11 = new nominotypical sub
**0 = unspecified
+
* ConceptChangeID, integer, 4 bytes, values in effect on completion of the change, permitted values:
**1 = unchanged
+
** 0 = unspecified
**2 = new
+
** 1 = unchanged
**3 = restored
+
** 2 = new
**4 = expanded
+
** 3 = restored
**5 = shrunk
+
** 4 = expanded
**6 = modified
+
** 5 = shrunk
**7 = terminated
+
** 6 = modified
**8 = transferred
+
** 7 = terminated
*OtherHistoryID, integer, 4 bytes, = tblTaxonHistory.TaxonHistoryID, identifier for the other history ID involved in a relationship change specified in RelatedHistoryID
+
** 8 = transferred
*RelatedHistoryID, integer, 2 bytes, = tblRelatedHistory.RelatedHistoryID, identifier for the type of relationship to OtherHistoryID
+
* OtherHistoryID, integer, 4 bytes, = tblTaxonHistory.TaxonHistoryID, identifier for the other history ID involved in a relationship change specified in RelatedHistoryID
*UserConfirmed, bit, 1 = user has confirmed data in this row or generated from user supplied data in tblCites
+
* RelatedHistoryID, integer, 4 bytes, = tblRelatedHistory.RelatedHistoryID, identifier for the type of relationship to OtherHistoryID
*UnreliableAssumption, bit, 1 = program used an unreliable assumption to create row
+
* UserConfirmed, bit, 1 = user has confirmed data in this row or generated from user supplied data in tblCites
*ArbitraryRow, bit, 1 = arbitrary row generated by program to resolve conflict, user resolution needed
+
* UnreliableAssumption, bit, 1 = program used an unreliable assumption to create row
*Note, text, 300 bytes maximum. When Status is set = 2, values for NomenclatorID and CiteRefID are set = 0, but those items are expanded to text in this column.  When Status is set = 3, the domain name of the split out species file is placed in this column.
+
* ArbitraryRow, bit, 1 = arbitrary row generated by program to resolve conflict, user resolution needed
*LastUpdate, smalldatetime, date and time row last changed
+
* Note, text, 300 characters maximum. When Status is set = 2, values for NomenclatorID and CiteRefID are set = 0, but those items are expanded to text in this column.  When Status is set = 3, the domain name of the split out species file is placed in this column.
*ModifiedBy, integer, 2 bytes, UserID of the signon that made the change
+
* Status, integer, 1 byte, status of the row
*Status, integer, 1 byte, status of the row
+
** 0 = active
**0 = active
+
** 1 = dormant, used for deleted nominotypical subs, which might be re-instated at a later time
**1 = dormant, used for deleted nominotypiical subs, which might be re-instated at a later time
+
** 2 = artifact, used for rows erroneously added.  The row cannot be deleted once TaxonHistoryID has been exposed in a GUID for a taxon concept. But does that ever happen?
**2 = artifact, used for rows erroneously added.  The row cannot be deleted once TaxonHistoryID has been exposed in an LSID or other GUID for a taxon concept.
+
** 3 = moved to other species file identified in Note
**3 = moved to other species file identified in Note
+
** 4 = moved out of scope
**4 = moved out of scope
+
* LastUpdate, smalldatetime, date and time row last updated
 +
* ModifiedBy, integer, 4 bytes, FileUserID of the signon that made the change
 +
* CreatedOn, smalldatetime, date and time row was created
 +
* CreatedBy, integer, 4 bytes, FileUserID of the signon that created the row
 
[[Category:TaxaTables]]
 
[[Category:TaxaTables]]
 +
[[Category:Tables]]

Latest revision as of 15:18, 11 May 2014

tblTaxonHistory, history of concepts and nomenclature for protonyms. This is used only for taxa at genus rank or lower.

  • TaxonHistoryID, integer, 4 bytes, primary key, identifier for taxon name and concept.
  • TaxonNameID, integer, 4 bytes, = tblTaxon.TaxonNameID, identifier for the monomial name (protonym) associated with the history.
  • FileID, integer, 4 bytes, = tblFiles.FileID, the species file the row is associated with. This column is being added in late 2013. Old rows with Status = 2 (artifact) remain with FileID = 0.
  • SeqNum, integer, 2 bytes, sequence number within this TaxonNameID, 1-based values without gaps.
  • NomenclatorID, integer, 4 bytes, = tblNomenclator.NomenclatorID, identifier for binomial name associated with the history.
  • CiteRefID, integer, 4 bytes, = tblRefs.RefID, identifier for the reference that defined the nomenclatural or concept change. May = 0 if change comes from other source explained in note or if the reference has not been identified.
  • NewNameStatusID, integer, 4 bytes, status of name when changed
    • 0 = unspecified
    • 1 = unchanged
    • 2 = new taxon name
    • 3 = made a synonym
    • 4 = made valid or temporary
    • 5 = new combination
    • 6 = name deleted with no related name
    • 7 = name deleted because of duplicate protonym, related name can be found in tblRelatedHistory
    • 8 = genus or species lowered to nominotypical sub
    • 9 = nominotypical sub raised to genus or species
    • 10 = name replaced by nominotypical sub
    • 11 = new nominotypical sub
  • ConceptChangeID, integer, 4 bytes, values in effect on completion of the change, permitted values:
    • 0 = unspecified
    • 1 = unchanged
    • 2 = new
    • 3 = restored
    • 4 = expanded
    • 5 = shrunk
    • 6 = modified
    • 7 = terminated
    • 8 = transferred
  • OtherHistoryID, integer, 4 bytes, = tblTaxonHistory.TaxonHistoryID, identifier for the other history ID involved in a relationship change specified in RelatedHistoryID
  • RelatedHistoryID, integer, 4 bytes, = tblRelatedHistory.RelatedHistoryID, identifier for the type of relationship to OtherHistoryID
  • UserConfirmed, bit, 1 = user has confirmed data in this row or generated from user supplied data in tblCites
  • UnreliableAssumption, bit, 1 = program used an unreliable assumption to create row
  • ArbitraryRow, bit, 1 = arbitrary row generated by program to resolve conflict, user resolution needed
  • Note, text, 300 characters maximum. When Status is set = 2, values for NomenclatorID and CiteRefID are set = 0, but those items are expanded to text in this column. When Status is set = 3, the domain name of the split out species file is placed in this column.
  • Status, integer, 1 byte, status of the row
    • 0 = active
    • 1 = dormant, used for deleted nominotypical subs, which might be re-instated at a later time
    • 2 = artifact, used for rows erroneously added. The row cannot be deleted once TaxonHistoryID has been exposed in a GUID for a taxon concept. But does that ever happen?
    • 3 = moved to other species file identified in Note
    • 4 = moved out of scope
  • LastUpdate, smalldatetime, date and time row last updated
  • ModifiedBy, integer, 4 bytes, FileUserID of the signon that made the change
  • CreatedOn, smalldatetime, date and time row was created
  • CreatedBy, integer, 4 bytes, FileUserID of the signon that created the row
Personal tools
Namespaces

Variants
Actions
Navigation
Species Files
Wiki
Toolbox