Change an ELCODE

For species: Element codes (ELCODEs) will continue to be used as unique identifiers for Elements in Natural Heritage Programs and Conservation Data Centres (NHPs/CDCs) using the Biological and Conservation Data system (BCD). Since the codes will no longer be information rich (and therefore do not need to reflect changes to classification, such as changes in family, genus, or classification level), ELCODEs should not be changed in Biotics. This will help to avoid unnecessary code changes in BCD databases, and facilitate matching of Element records during the data exchange process between NHPs/CDCs and NatureServe Central Databases.

ELCODEs should only be changed when a revision of the standard classification requires the replacement of an existing standard Element with a new Element with the same name, but only a slightly different circumscription. In this case, if the Element concept (and corresponding data) as it is perceived by most NHPs/CDCs will not change, the old ELCODE can be moved to the new Element Tracking record in order to avoid the need for code changes in most databases. However, this method may only be used if the record for the Element being replaced is to be archived (inactivated); if it will remain in the database as a nonstandard Element, the ELCODE must remain the same in that record and the new record must receive a new ELCODE. Having an old ELCODE refer to the new Element could result in confusion if the old Element still exists in the active database (with a new ELCODE, as required by business rules).

For communities: Element codes (ELCODE) will continue to be used as unique identifiers for ALL Central Ecology community Elements. An ECLODE may be changed when the Classification Status of an Association-level type is changed. For example, a change from a nonstandard Park Special (CEPS) or Proposed (CEPP) type to a standard (CEGL) type. In these cases, only the prefix should be changed; the numeric portion of the code should be retained. Information on the obsolete code should be entered into the Element History grid.

 

NOTE: Should the ELCODE be changed of an element for which there are associated Element Occurrences, you may also want to manually update the EO.eo_num_bcd value(s) via SQL, to keep the data in sync with the ELCODE. That being said, Biotics 5 does not populate eo_num_bcd nor display the data and therefore any values in this field are legacy data carried over from Biotics 4.

See also:

Assign a new ELCODE

SQL queries for finding the next available ELCODE

of