-
Notifications
You must be signed in to change notification settings - Fork 13
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
New publisher not "filtering" #39
Comments
That is a bug that I have introduced recently. And only you see it because you are the only ones using dataset search I believe. I've created an issue that might help us scope the suggest gbif/registry#427 |
This issue gbif/registry#421 becomes a real nuisance in this speciifc case |
Some ideas:
But by the behavior we are having I realize this is a criterion based on the occurrences and not on the publisher.
I hope these ideas can help, if not let me know and I will try to look for other strategies. |
{
"key": "publishingCountry",
"type": "equals",
"value": "CO"
} This part is a part of the configuration for occurrences and will include all datasets with occurrences, no matter the Core. Dataset search can be configured very differently. Your dataset search is configured to show datasets published from Colombia https://github.com/gbif/hp-colombian-biodiversity/blob/master/_includes/js/config.js#L49 For dataset search we rely on the features of that API. And that does not allow us to include all datasets that have e.g. either a single occurrence point in Colombia or is published from Colombia (including datasets without occurrences). Another challenge is then suggest. When suggesting for example publishers, then we rely on optimised suggest endpoints that respond quickly and have some degree of fuzzy matching on the text input. But those do not allow us to do any filtering of the suggestions. That is the same problem we have in occurrence search where a dataset suggest would suggest al possible datasets known to the GBIF API. I found a way to circumvent that issue by creating APIs specific to this project and by accepting worse matching, but at least ensure that the suggestions was part of the data for that website. So previously a search for |
Thank you for the explanation. In response to:
I understand it is not posible now, but can it be something to work during the second phase of the hosted portlas? I think this is something that other portals will also need. For the second idea. that now I see it more as a need, do you have some thoughts? :
|
We published this cheklist from a new publisher , on June 30, when we search for the cheklist name or publisher using the free text filter in or portal we get the expected result but when we search for publisher we don't get any hit:
Free text search:
Publisher search:
PD: probably this is for another issue, for the datset view is there a Dataset title filter avilable? when i go to more I can't see one.
The text was updated successfully, but these errors were encountered: