StocksAndFisheriesKB

Sorry for the delayed answer but we were busy with the FAO Symposium then I was on duty travel.
I checked the above examples and seems fine.
Also, in the tag list, I see that those tags are no longer duplicated, am I correct?

If so, then the ticket can be closed unless other comments.

Hi Aureliano,

Aureliano Gentile wrote:

Sorry for the delayed answer but we were busy with the FAO Symposium then I was on duty travel.

don't worry...

I checked the above examples and seems fine.
Also, in the tag list, I see that those tags are no longer duplicated, am I correct?

I've not performed any action regarding the tag list and tags duplicated... I identified and fixed a bug (for tag containing multiple spaces, see #18090, those tags now are searchable) in the querying system provided by CKAN.
If you notice repeated tags in the tag list (belonging to the same GRSF record), please provide us with the record/s involved and we will take actions needed to check the issue in the source json or grsf updater service.

If so, then the ticket can be closed unless other comments.

In my opinion, this ticket can be closed.

As regards species name, they are shown exactly as they appear in their original sources.
However, we could normalize them on the GRSF KB side so that they appear properly (Genus with first capital letter, and specific epithet in lower case). I think this would resolve the issue (at least for species tags)

Hi Aureliano, Yannis

Aureliano Gentile wrote:

Thanks, for example these two tags are the same but they do retrive different records:

Code BLU Classification System ASFIS Scientific Name Pomatomus saltatrix
Code BLU Classification System ASFIS Scientific Name pomatomus saltatrix

In any case, all tags with scientific names should have the first letter of the first word in capital and all the rest in lower case.

as reported by Yannis, after a normalization performed on the GRSF KB side, so before submitting a record in the GRSF/GRSF-ADMIN Catalogue, all tags with scientific names will be identical.

Regarding TAG creation, upper or lower case could be ignored. But I understand it is not straight forward to build the rule identifying the right way to do it. Unless we put everything in upper case or in lower case...

just a clarification as regards filtering for TAG and if it should be case sensitive or case insensitive.
Now, on catalogue side, the filtering for TAG is case sensitive but there should be no problems from the technical/technological point of view to change/update it to case insensitive one (by updating the indexing schema).

In my opinion, the question is... what is the main use and semantic of a TAG in the GRSF/GRSF-ADMIN context?
In my understanding, if a TAG attached to a GRSF Record refers to scientific "data" (e.g. species scientific name, fao area, etc.) a normalization on such data should be performed before of submitting them in the GRSF/GRSF-ADMIN catalogue and the Catalogue should provide (as it is now) the filtering for TAG that is case sensitive.

Thanks to all, I understand that normalization should take place in the knowledge base and leave the TAG mechanism as it is now. if so, then it is FORTH to follow up, I guess into a new ticket and this one can be closed.