Location ID problems in Lynx.Wildbook

Support
, ,
1

Hi all,

I’m running into a small issue with bulk imports. When I use "Vale do Guadiana" as the locationID, the encounters don’t seem to get saved under that location.
https://lynx.wildbook.org/import.jsp?taskId=bac01a20-7f71-40a3-aeae-b9f14120cbec

However, if I use "Región Vale do Guadiana" as the locationID, it seems to work correctly.
https://lynx.wildbook.org/import.jsp?taskId=1f196bd8-b700-434c-aa45-18fb3c46f8e4

I checked the locationID.json file (from this link) and I see this entry:

{
  "name": "Vale do Guadiana",
  "id": "Región Vale do Guadiana",
  "locationID": []
}

So it seems the correct value to use in the bulk import is "Región Vale do Guadiana", as that’s the actual ID. Is this correct?

To avoid confusion, wouldn’t it make more sense to have both the "name" and the "id" as "Región Vale do Guadiana"? Right now, the inconsistency between "name" and "id" might lead to mistakes, especially since in other cases the name and ID are often the same.
image

image
image1311×167 32.1 KB

Any help or clarification would be appreciated!

Thanks in advance,
Antón

2

Hi @AntonAB

We actually have a ticket that we’re working on to correct this, but it’s taking a while to complete due to the manual nature of the fixes.

When Wildbook locationID.json files have conflicting values in the name and id fields, it creates the discrepancies you’ve mentioned here. Wildbook considers whatever is in the id field to be the “correct” location and the name field is what displays in the location ID drop-down menu of the site.

For the time being, you’ll want to use “Región Vale do Guadiana” in your bulk import. When the location ID file is fixed in your Wildbook, I’ll post about it in Community.

1 Like
3

Hi @Anastasia,

Thanks for the quick answer.

I sent you an email with an option to upload the locationID.json.
I hope that email found you well.

Best,
Antón

1 Like