Skip to content

Latest commit

 

History

History
46 lines (33 loc) · 1.84 KB

physical_entity.md

File metadata and controls

46 lines (33 loc) · 1.84 KB

Component Description: Physical Entity

Specific scope of the component

Previously called Material Samples.

What does the component do? (envisioned feature set)

Definition

A physical result of a sampling event.

In natural history collections, the material sample is typically collected, and either preserved or destructively processed. (from Darwin Core)

Has links to

  • Collection Event(s): a physical entity comes from a single collecting event. In case of merging entities to one physical entity, parent-child relations between physical entities (each having a collecting event) would be used.
  • Catalogued Object(s): many to many, a catalogued object may consist of several physical entities (with own identities) and physical entity may comprise several collection objects
  • Files and Multimedia
  • Preparations
  • DNA Sampling & Sequencing (Need to look at this use cases)
  • Loans and Transactions
  • Physical storage location(s)

Potential fields

  • Import Permit Tracking (CFIA for AAFC)
  • Field number or Other IDs of all sorts
  • Substrate type: air, water, soil
  • Current state of the physical entity (preserved, destroyed, contaminated, consumed, lost ...)
    • Link to preparation and protocol (when applicable)
    • History of State of the physical entity with date and agent
  • Amount? weight/ countable unit (3 parts of something) ( Talk to Falko for more)
  • Protocols to capture something from the collection event
  • Stores the preparation details specific for a Material Sample
    • example?
  • Stores the provenance of subsampling events
    • Example: living material that is periodically sampled, each subsequent sample needs to have at minimum a link to a parent sample

What does the component not do? (excluded features to avoid misperception / confusion)

Lead of development team

Link to component specs repo