Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using new establishmentMeans causes "distribution:invalid" warning on GBIF #35

Closed
peterdesmet opened this issue Sep 14, 2017 · 4 comments
Assignees
Labels

Comments

@peterdesmet
Copy link
Member

The checklist taxa get a distribution:invalid tag on GBIF (e.g. https://www.gbif.org/species/134086869). We have to figure out why.

@peterdesmet
Copy link
Member Author

Issue repported at gbif/portal-feedback#562

@peterdesmet
Copy link
Member Author

@qgroom, so... establishmentMeans values are actually verified by GBIF and have to be one of these values: http://rs.gbif.org/vocabulary/gbif/establishment_means.xml (= the required data type).

If a value fails it gets distribution:invalid and the establishmentMeans info is not available via the API, which is the case for all our values (like escape:horticulture). We of course want to update that controlled vocabulary, so these actually represent a pathway (like escape:horticulture), but it seems that 1) that will generate some issues for the validation of all data currently out there and 2) might take a long time to implement.

What do we do in the meantime?

  1. Leave that value empty and add it as descriptions (in which we can be freeform)
  2. Be fine with not being able to pull that info from the GBIF API until the whole vocab has been ratified and implemented?

@peterdesmet peterdesmet changed the title Figure out "distribution:invalid" warning on GBIF Using new establishmentMeans causes "distribution:invalid" warning on GBIF Oct 19, 2017
@peterdesmet
Copy link
Member Author

Opted to leave the establishmentMeans values as is: so these will still create a distribution:invalid flag -- which should remind us that this is still a vocab implementation issue at GBIF (+ also recorded at gbif/portal-feedback#562)

In order to be able to access the pathway information already via the GBIF API, it is now also added in the Description extension: see #40

@LienReyserhove issue can be closed once dataset is republished and we have tested API.

@peterdesmet
Copy link
Member Author

Now solved. The original example at the beginning of this issue no longer exists (because we have updated our taxonIDs), but see e.g. https://www.gbif.org/species/141265785.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants