etaxonomy module - fieldmuseum/EMu-Documentation GitHub Wiki

FAQ | Q&A | ISSUES | PROJECT | LUTS

Pending Structural Changes : Yes

What does an etaxonomy record represent?

A Taxonomy record represents the legal or ethical documentation related to a given set of museum work or collections. It can represent one of the following:

For Biological collections, the Taxonomy module represents a repository of all Linnaean taxonomy and their associated data. Each record represents one taxon and its citations, descriptions/traits, protections, histories, and ranges/distributions. Relationships between records can be hierarchical, synonymous, or both.

For Physical Geology collections, a Taxonomy record represents levels in mineral and meteorite taxonomies.

Taxonomy records are used as a specimen “description” in the Catalogue, and as a taxonomic ordering system for collections and repository of ongoing taxonomic research.

Current Sub class Status

Subclassed?: Yes

Tab Switching:

  • Column Name: ClaApplicableCode
  • Lookup List: Taxonomic Code
  • Tab switching: Yes

Record Types:

  • ICZN | ICZN-P
  • ICN | ICBN-P | ICBN
  • Minerals
  • Meteorites

Record Structure:

Flat. (There are no attachments to records of the same module.)

Hierarchical. A parent/child relationship inherent to the nature of a Taxonomy record and its data.The record itself inherits data from its parent and/or there may be logic that changes data, based on the presence of a parent/child attachment. Network. Synonymies involve attachments to records of the same type Sequential. There are attachments to records of the same type, and a defined sequence-order between attached records.

Fields

Mandatory

  • ClaApplicableCode
  • ClaKingdom

Unique

Ditto Skip

Insert Defaults

Query Defaults

Attachment Field Display Values

  • AutBasionymAuthorsRef_tab.NamTaxonomicName
  • AutCombAuthorsRef_tab.NamTaxonomicName

Software Dependencies

Resources -> Tools

Page Views

  • SynonymView: nuthatch (shared with multiple collections/manager/intern groups)
  • SynView2: jjones (shared with Admin)
  • SynView3: kwebbink (shared with Admin)

Summary String(s)

Default

irn

e.g. (irn xxx):

Applicable Code (ClaApplicableCode)

= ICZN, ICZN-P, ICN, ICBN, ICBN-P

ClaScientificName

e.g. (325063):  Graphium xenocles (Doubleday, 1842)

= Minerals

“[“ + ClaMinDanaClass + “.” + ClaMinDanaType + “.” + ClaMinDanaGroup + “] - “ + ClaMinChemistry

e.g. (irn 570236):  [ 52.2.2.9 ] - CCa10(Mg,Fe)2Al4Si9O34(OH)4

= Meteorites

“[Meteorite] - “ + ClaScientificName

e.g. (irn 681839):  [Meteorite] - L7

STRUCTURAL CHANGES: Rationale

Reason(s) for Change Request version 6.3(https://drive.google.com/file/d/13BJ1rH1UyH1xHPkG9ued1xVCIL2hUxr1/view?usp=sharing)]

Status

  • Version 9 - 4 August 2023: In test. [Testing Notes]
  • Funded - Yes [IT (IMLS Empowered)]
  • FMNH Specific customisation

Details

  • Updates for identification keys
  • Rare and Endangered, CITES tracking for loans across departments
  • DwC traits