Location ID in ACW

jason · June 16, 2020, 5:46am

Fix deployed. It was a mapping display issue but should not affect the actual value.

Please let us know if it’s resolved.

Thanks,
Jason

jason · June 19, 2020, 2:34am

Hi Maureen,

I found the issue in our mapping file. "Africa - West " was mapped to “Africa - All”. This issue only affected manual submission. The bulk uploader will accept any value you give it for Encounter.locationID (but see below because there is a fixed list of values that should be used).

For this Encounter:
https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=1df9b649-836a-4c20-9da5-5818485a15c8

The value remains displayed as “Africa - All” because it was erroneously recorded in the database that way via direct submission. If you set it to Africa - West now, the value will take.

One long-term consideration: Encounter.locationID is a fixed vocabulary defined in this file for ACW here:

github.com

WildMeOrg/Wildbook/blob/carnivore/src/main/resources/bundles/locationID.json

{
  "description": "Hierarchical Encounter.locationID list in Wildbook",
  "source": "http://en.wikipedia.org/wiki/List_of_seas",
  "locationID": [

	{"name":"Africa - All","id":"Africa","locationID":[

		{"name":"Africa - South","id":"Africa - South","locationID":[


			{ "name":"Angola", "id":"Angola", "locationID":[] },
			{ "name":"Botswana", "id":"Botswana", "locationID":[] },
			{ "name":"Mozambique", "id":"Mozambique", "locationID":[] },
			{ "name":"Namibia", "id":"Namibia", "locationID":[] },
			{ "name":"South Africa", "id":"South Africa", "locationID":[] },
			{ "name":"Zambia", "id":"Zambia", "locationID":[] },
			{ "name":"Zimbabwe", "id":"Zimbabwe", "locationID":[] }
			
			
			]},

This file has been truncated. show original

It is meant to grow and evolve as more study sites are added. And it allows names to be more descriptive and change without changing the value.

For every study site there is a friendlier, hierarchical “name” that can be changed at any time in the file. There is also an “id” value, which is what gets recorded in the database. Generally they map 1-to-1 name=value. Where there’s some amount of older data with an older “id”, the name may evolve and differ while the “id” does not to keep the data consistent. The only difference between name and id right now is:

name: “Africa - All”
id: “Africa”

The id is always the value to use with bulk import. All of the mappings look clean now with distinct id values.

Thanks,
Jason

tanyastere · July 6, 2020, 10:50pm

@ACWadmin1,
can you confirm, did the mapping changes @jason completed resolve the issue? Are you able to use the id when uploading now?

Tanya

ACWadmin1 · July 10, 2020, 6:06pm

We have stopped doing bulk uploads while we wait for answers / fixes to the data issues we reported a couple of weeks ago - occurrence ID + alternate ID both not displaying consistently in all records uploaded; negative GPS not being uploaded as negative (putting the location in Chad instead of Botswana).

jason · July 16, 2020, 3:57pm

Bulk Import-related issues are being addressed elsewhere, including a new code deploy last night with fixes. Marking this as resolved until we hear back otherwise on this specific issue.