The value under GBIF region (e.g. for TZ) reads "e...
13446
Reporter: ahahn
Type: Bug
Summary: The value under GBIF region (e.g. for TZ) reads "e...
Priority: Blocker
Resolution: Fixed
Status: Closed
Created: 2013-07-03 12:14:32.412
Updated: 2013-12-16 17:51:03.082
Resolved: 2013-07-04 11:48:14.03
Description: The value under GBIF region (e.g. for TZ) reads "enum.region, both in the green header bar and the Participant information tab
*Reporter*: Andrea Hahn
*E-mail*: [mailto:ahahn]]]>
Author: mdoering@gbif.org
Created: 2013-07-03 12:39:24.146
Updated: 2013-07-03 12:39:24.146
This is a missing region entry in the registry db for the tanzanian node:
http://api.gbif.org/node/abd95ca6-3959-4db9-aaa6-2de1aeecf514
I would propose to make the region a mandatory field for a node to avoid this in the future. Alternatively we could also make the portal deal with null values for the region, but it seems like a simple field we should be able to maintain
Author: ahahn@gbif.org
Comment: Many of our associate participant nodes cannot be associated with a GBIF-region. If we make the field mandatory, we need an additional value that will play both with the header bar text ("A GBIF Voting Country Participant from Latin America") and the GBIF Region display in the participation and summary pages in the future (new) non-country member pages. In the short formulation, "N/A" or similar would work; in the header, such values would have to be suppressed ("A GBIF Other Associate Participant --from N/A--"). I agree we should be able to maintain the content for others where regional affiliation does exist. The authoritative region information is managed in the IMS and needs to be synchronised from there (manually or automatically). NB: the participant region of a node does not always follow geographical regions, but can be decided by the node to optimize self-organization and collaboration within the regional group.
Created: 2013-07-03 16:57:51.674
Updated: 2013-07-03 17:13:20.321