Closed jlegind closed 1 year ago
From Slack: Locality has now been expanded with two pick lists, namely "Broad Geographical Region" and "BGR Source" for adding the respective annotations. I understood the idea is to initially add corresponding localities with the same name for the fast mass digitization of objects. Then, in time, each object could have their specific locality name specified, while the BGR is retained. Note: I assigned locality fields text1 and text2 respectively for this purpose.
From mail by @PipBrewer :
So far the sources for broad geographic regions are: • Major biogeographical region (Hansen 1998, World Catalogue of Insects) • TBU floristic district (Hartvig 2015) • Major biogeographical region (NHMD herbarium) • Major biogeographical region (Aarhus herbarium)
I didn't quite get to finish this, but this will be easy pickings for the next sprint.
@PipBrewer I'm a bit stuck with this one and not sure what I need to do anymore.
Here are the lists. Looks good to me.
Thanks! Are these only for NHMD?
No. Look atthe source as you go down the list.
Source | Institution | Collection |
---|---|---|
Major biogeographical region (NHMD herbarium) | NHMD | Botany |
TBU floristic district (Hartvig 2015) | NHMD | Botany |
Major biogeographical region (Hansen 1998, World Catalogue of Insects) | NHMD | Entomology |
Major biogeographical region (Aarhus herbarium) | AU |
As just mentioned, yes the two fields are linked. Once BGR is selected, the source should be automatically filled in on Specify
Finished.
Issue
Sorting out the broad geographic regions. Specify needs Locality tweaked to accommodate the geographical concepts. The TBU districts were later removed from the App DB though.
Adding fields in Specify so that the geography can be added. Field 1 = The broad geographic region/ TBU code or name Field 2 = Source of field 1