Hi Jörg,this is intended behavior. These contacts are rendered as associate parties in the portal project block:
The contact type is not required. And even though we try to have a primary administrative contact that is also not a requirement.
But in this specific case our tapir "metadata synchronisation" could be a bit more clever and detect the type.
Markus
Hi guys,
I'm using the API to get dataset metadata from the registry (http://api.gbif.org/v0.9/dataset).
Each dataset entry has a 'contact' element, which is a list of contacts. Usually, each contact has a certain type. In the given example in the documentation, there are two contacts, each of type ADMINISTRATIVE_POINT_OF_CONTACT:
http://api.gbif.org/v0.9/dataset/4fa7b334-ce0d-4e88-aaae-2e0c138d049e/contact
However, paging through the datasets, I hit contacts that somehow look different. For example, they don't have a type, which breaks a script if you want to find the primary administrative contact, for example:
http://api.gbif.org/v0.9/dataset/570489ac-e114-4a17-9340-2e01ee7d9ee3/contact
Is that intended? Or is it leftovers from the old registry?
Cheers,
Jörg
---//------------------------------------------------------------
Jörg Holetschek
Coordinator Biodiversity Data Networks
Botanic Garden & Botanical Museum Berlin-Dahlem
Dept. Biodiversity Informatics
Königin-Luise-Str. 6-8, D-14195 Berlin
+49 (0)30 838-50150, j.holetschek@bgbm.org
------------------------------------------------------------//---
_______________________________________________
API-users mailing list
API-users@lists.gbif.org
http://lists.gbif.org/mailman/listinfo/api-users