StocksAndFisheriesKB

I'm investigating the feasibility.

The actual analysis is the following:

• I'll improve gcat to support more options for automatic tagging and grouping;
• I'll create a new GRSF service which in turn uses gcat;
• The new service will use configurations to map the field received from the KB to the format expected by gcat/CKAN. This will allow making changes easily and, in most cases, without the need to modify the code for the service. I want to highlight that even though it will be easy to change the configuration, the backend (i.e. CKAN) does not support it, so everything must be republished.

Hopefully, the KB does not have to change anything apart from some minor changes in the URLs
For example, the current URL for a FIRMS Fishery Record is /grsf-publisher-ws/firms/fishery and will be /grsf-publisher/fishery/firms.
In other words:

• the service base name will change from /grsf-publisher-ws/ to /grsf-publisher/
• the source will be after the main type eg. from /firms/fishery to /fishery/firms

@marketak@ics.forth.gr is it for you easy to change the URLs in the way I have proposed especially for source/type swap?