GRSciColl - make suggestions searchable by country

[ManonGros]

As we get more GRSciColl mediators, it would be helpful if they could search suggestions by country.
Sometimes, a mediator can miss notifications or there might be several mediators for one country so you need to check which suggestions were applied.
It would be helpful if they could just go here: https://registry.gbif.org/suggestions/institutions?status=PENDING and select the country they want to check.

Would that be possible @marcos-lg, what do you think?

[marcos-lg]

We don't have a column for the country in the DB so the filtering should be done after retrieving the results. We could implement it in the api but it could also be done directly in the UI, there wouldn't be too much difference.

[ManonGros]

thanks @marcos-lg
An alternative could be to filter the suggestions by users that can apply them. Such that if you are logged in the registry you could see all the suggestions that you can review.
What do you think? would it be better?

[marcos-lg]

Both are good. I mean, for both cases it has to be implemented at the api level and not at the query label, so we can do any or both of them. Whatever is more useful.

[ckotwn]

@marcos-lg on the landing page of pending suggestions I can see the country attribute at https://registry.gbif.org/suggestions/institutions?status=PENDING. I suppose the information is suppose to be there when an user submit it. Did you mean that country information isn't stored in the DB?

Otherwise for implementing this feature I think it'll be indeed useful if country is available as a filter option.

[marcos-lg]

Yeah, the country is there but it is "calculated" when retrieving the suggestions. But we can still add a country filter.

[marcos-lg]

I'm going to transfer this issue to the registry-console since storing the country in the DB is troublesome because if the country of the entity changes we'd have to update the suggestions to keep it consistent. And doing the filter with the calculated value in the api is also troublesome because of the paging. Therefore, I think it's simpler to do the filtering directly in the UI.

[MortenHofft]

@marcos-lg I would have to pull all suggestions/results into the browser to filter them. Currently around 900 of them. I do not think that is a good solution either. And it will only become worse as the list of suggestions grow over time.

[marcos-lg]

Ok, it's the same problem as in the backend. The only solution is to store the field in the DB but we'd have to keep it synced with the collection/institution, i.e.: if the country changes in the collection/institution we need to change it in the suggestion too, so not sure if it's worth the effort.