You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tschudip unless you have good reasons to not fill locality, could you then use that over verbatimLocality?
@tucotuco will know better, but I believe verbatimLocality should be used as a supplement to locality. locality being the default field. verbatim as a supplement to tell you what interpretations if any have been made. But the documentation is less clear about that for verbatimLocality. It was very clear for verbatimIdentification
The verbatimLocality is like all other Darwin Core verbatim fields. It is meant to contain the data as captured as close to the moment of the Event as exists. The locality field is, generally speaking, a version of that that may or may not be elaborated on or corrected. In any case, it is recommended to fill both, even if they are the same.
https://dwc.tdwg.org/terms/#dwc:verbatimLocality
@tschudip unless you have good reasons to not fill locality, could you then use that over verbatimLocality?
@tucotuco will know better, but I believe verbatimLocality should be used as a supplement to locality.
locality
being the default field. verbatim as a supplement to tell you what interpretations if any have been made. But the documentation is less clear about that forverbatimLocality
. It was very clear forverbatimIdentification
NB: this is essentially the same comment as in #100 about https://dwc.tdwg.org/terms/#dwc:verbatimIdentification
The text was updated successfully, but these errors were encountered: