Skip to content

esites module

Sharon Grant edited this page Nov 11, 2021 · 35 revisions

What does an esites record represent?

A record in the sites module represents a place and is a record of a position or point in space. There is no time element associated with a site record other than as a result of a place name no longer being used commonly. Detailed time elements such as collection date and/or chronostratigraphy should be captured at the catalogue level as part of a collection event or stratigraphy attachment

Tab Switching:

  • Column Name: SitRecordClassification
  • Lookup List: Site Record Classification
  • Tab switching: Yes

Record Types:

Aquatic

  • An aquatic site record refers to a place that is located within a body of water, freshwater or marine. If that place is maritime and falls outside of a national territorial boundary then the continent should be set to “International Waters”.

Cultural

  • A cultural site record refers to a place, region or area which has particular significance to a cultural group.

Terrestrial

  • A terrestrial site record refers to a place that falls on the land.

Record Structure:

Parent/Child; Hierarchical; Is a special case of a Parent/Child: Here there is a parent/child relationship inherent to the nature of the 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.

You can use them in combinations to fully document the place you are describing. There are four:

  • 2 Terrestrial ** Political ** Island
  • 2 Aquatic ** Freshwater ** Aquatic (Nautical/Maritime)

Resources -> Tools

  • Search GeoLocate - County/City
  • Search GeoLocate - Precise Locality

STRUCTURAL CHANGES: Rationale

Reason(s) for Change Request [version 2]

Status

  • Version 5.1
  • Funded - [In live]
  • FMNH Specific customisation

Details

  • Standardise the use of the module to make it more efficient and reflect consolidation of internal processes and workflows. Prepare for newer versions of EMu by not transferring bad data structures and dirty data.
  • Implement a parent/child structure that more closely ressembles a hierarchical taxonomic hierarchy. This will allow synonymization and better handling of equivalent names for example historical place names.
  • Allow us to rationalise and de-duplicate records
  • Fix existing bugs: ** ????