Open PaulKiddle opened 4 years ago
Host fields:
- host
- host_other
- host_type
These should map to associatedTaxa but we need to check and use a suitable ontology to describe the association. Example below:
"host":"Quercus alba", "parasitoid of":"Cyclocephala signaticollis" | "predator of":"Apis mellifera"
Locality fields:
- locality
Should probably map to verbatimLocality but check with Louise this is correct for historical usage.
- country
Should map to country.
- precise_locality
Should map to locality.
Collector fields:
- collector_initials
- collector_surnames
Darwin Core deals with people in a fairly simple way an just uses recordedBy for both of these fields. Darwin Core recommended best practice is to separate the values in a list with space vertical bar space ( | ). We may want to keep these separate and consider concatenating them in an export.
Collection date fields:
- collection_day
Should map to day.
- collection_month
Should map to month.
- collection_year
Should map to year.
- collection_range
Should use two fields startDayOfYear and endDayOfYear - these expect ordinal days so don't forget leap years!
These correspond to the Event class in Darwin Core.
"Type status: should probably use a controlled vocab."
In the app we have the ICZN recognised type status as options as well as an "other" option for the unrecognised statuses
Locality fields: There are only two fields to map: "Country" and "Precise locality" - the other "locality" field was for categorising the locality = real/unreadable/artificial (not essential and can be captured in notes if necessary)
Precise locality: should map to verbatimLocality
Country: Should map to country
Sex/Stage fields: These form part of the Occurrence class:
- Count
Corresponds to individualCount
Note: Stage and sex need separating (and may require logic to make it easier for entry - an egg would not have a determinable sex value).
- Stage
Corresponds to lifeStage but different projects will use different controlled vocabularies.
- Sex
Corresponds to sex but different projects will use different controlled vocabularies.
Other:
@Allan-Louise we should probably discuss some of the other potential Darwin Core terms we may want to use.
Numbers (registrations):
I think we have covered the majority of fields for Entomology. Other collections would have other fields i.e. Botany - collector number, geographical region (26 regions) etc; Palaeo - stratigraphy etc
Fields as named in the user interface:
Host fields:
Locality fields:
Collector fields:
Collection date fields:
Registration Number:
Type status:
Sex/Stage:
Other:
These can be altered or combined on the backend where there's not a 1-1 mapping with a DWC field