ecollectionevents module

FAQ | Q&A | ISSUES/closed | LUTS | data cleanup | Workflows | STANDARDS

Pending Structural Changes

What does an ecollectionevents record represent?

A specimen-/data-gathering event that occurs at some defined location at some defined time, by some person/party, using a defined method. Collection Event records bring together all collection event-related data (The Who? When? Where? How?) in order to attach to and link together all specimens collected/observed in the same event.

Current Sub class Status

Subclassed?: Yes

---

Tab Switching:

• Tab switching: Yes

• Default: Tabs: AllCol1Tab, AllCol2Tab, AllHabTab, AllTasTab, AllMedTab, AllSecTab, AllAdtTab, AllAdmTab

• Column Name: ColCollectionType

• • Lookup List: Collection Type: Level 1
• • • Value: Terrestrial
• • • • Tabs: +AllTerTab
• • • Value: Aquatic
• • • • Tabs: +AllAquTab, +AllAqu2Tab

• Column Name: ColCollectionMethod

• • Lookup List: Collection Method: Level 1
• • • Value: Excavation
• • • • Tabs: +AllExcTab

---

Record Types:

Aquatic

• Collection event occurred in water, whether fresh or saltwater. Corresponds to the collection of one or more physical specimens and may be related to an observation.

Human Observation

• An output of a human observation or sighting in the wild. May or may not also be represented by a physical specimen in a collection.

Machine Observation

• An output of a automated machine observation process (e.g., camera trap). May or may not also be represented by a physical specimen in a collection.

Terrestrial

• Collection event occurred on land, but not below surface-level. Corresponds to the collection of one or more physical specimens and may be related to an observation.

Excavation

• Collection event occurred below ground. Such as a geological core or archaeological excavation. Depth is relative to surface-level of the dig.

Sighting

• Only used if the record cannot be assigned to either Human Observation or Machine Observation

---

Record Structure:

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

---

Fields

Mandatory

Unique

Ditto Skip

Insert Deafults

Query Defaults

---

Software Dependencies

---

Resources -> Tools

• NONE

---

Summary String(s)

Requests and updates to the summary string should be submitted as issues and tagged esites. When approved they should be documented in structural changes.

Default

“[“ + ColCollectionEventCode + “] ” + ColSite.SummaryData + “ “ + ColSiteQualifier + ColParticipant_tab.NamLast(ALL) where ColParticipantRole_tab(ALL) = “Collector” + “; ” + ColDateVisitedFrom

e.g.(1688334) - [DSB 4087] Asia, Philippines, Luzon, Camarines Norte Prov: Labo Municipality, Barangay Tulay na Lupa, 0.25 km N, 0.25 km W East peak Mt Labo. 1413m [LL]; Balete; 10 May 2006

Security Department (SecDepartment_tab)

Contains “Botany”

ColParticipant_tab.NamLast(ALL) where ColParticipantRole_tab(ALL) = “Principal Collector” +“ [“ + ColCollectionEventCode + “]; ” + ColDateVisitedFrom If ColDateVisited NOT= ColDateVisitedFrom

• ” - “ + ColDateVisitedTo

• “ - “ + ColSite.SummaryData + “ “ + ColSiteQualifier

  e.g.(2900121) - Sagástegui Alva [14929]; 28 Jul 1993 - South America, Peru, Cajamarca

---

STRUCTURAL CHANGES - Rationale (Most recent first)

Reason(s) for Change Request [See ecatalogue collection tab development]

Status

• Version v9
• Funded - [IT]
• FMNH Specific customisation

Details

• ecatalogue development to cleanup and rationalise the autogeneration of collection events from the catalogue across all departments.

---

Reason(s) for Change Request [version 3]

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: ** ????