Hi @maggieliebich and @tanyastere
So from what I can see here, I think there’s been a bit of miscommunication.
Right now, we already have a labelled key word for habitat obscurity with options light, medium, and thick (referring to bush, and abbreviated LB MB and TB on our field data sheets). What Rosemary then requested, is a further level of distinction between whether the dominant bush type is euclea, acacia drep, or mixed bush.
I don’t see why, if we already have a distinction made between light, medium, and thick, it needs to be reiterated as a prefix to the dominant type e.g. “LB Acacia Drep.” So that means we just need that additional dropdown to specify the dominant type, given that the obscurity is already established, with options Acacia Drep, Euclea, and Mixed bush.
Now, as Tanya correctly pointed out, a bush_type keyword already exists, and we definitely don’t need both bush_type and dominant_bush_type as separate, redundant entities. Given this, I think the thing to do here is just add Encounter.mediaAsset0.bush_type to the bulk import spreadsheet, as suggested, and not create a new field.
That being said, it would be helpful if “thick bush” could be removed from the options for the bush_type keyword, as I think the overlap in scope with habitat_obscurity could lead to some confusion.
Thanks also Tanya for adding Ol Jogi as a new location ID.