seltmann
commented
4 years ago These are the documented fields from the Associate! proposal for updating Symbiota to handle biotic associations.
| associd | primary key (PK) |
|---|---|
| occid (required) | FK for base occurrence |
| occidassociate (optional) | FK for associated occurrence; used only when association is an occurrence managed within same Symbiota instance; associated occurrences managed within external systems (e.g. iDigBio, GBIF) can be represented using link in resourceURL and dynamicProperties fields. |
| relationship | controlled vocabulary will be used |
| basisOfRecord | controlled vocabulary defining the specific nature of the associate occurrence, which will often be different than the base occurrence (e.g. HumanObservation, LiteratureCitation, etc) |
| identifier | globally unique identifier (GUID) representing the association. Will typically be a UUID automatically generated by Symbiota, though can be over ridden when GUID was generated outside of the Symbiota environment. |
| resourceurl | URL of relationships that were established outside of the Symbiota environment |
| verbatimsciname | verbatim name which may be full scientific name, abbreviated name, common name, or other non-standard format. Name is indexed to taxonomic authority post import |
| locationOnHost | controlled vocabulary, linked out to ontologies |
| condition | controlled vocabulary, linked out to ontologies |
| dateEmerged | date/time field recording date and time of emergence |
| dynamicProperties | JSON string consisting key-value pairs representing any dynamic property of the association. This can be used to store extended DwC field data for the associated occurrence or custom properties that are specific to a certain association (e.g. gall number, color, etc). |
| notes | general notes |
neilcobb
evindunn
We proposed some database changes to Symbiota as part of the Assocate! Project. These are documented here.