API

[fxprunayre]

We will have part of the API exposed by GN4 (https://apps.titellus.net/geonetwork/doc/api/) and part of the API in microservices. How do we combined the 2? Is it needed?

Currently we are using swagger to build the openapi doc.

OGC API Records (https://github.com/geonetwork/geonetwork-microservices/tree/main/modules/services/ogc-api-records) will also provide an openapi doc that we are using to build the server code

[pvgenuchten]

Over time methods of /geonetwork/doc/api/ will be migrated to dedicated microservices. Some methods may actually move from /geonetwork/doc/api/ to /ogcapi, even if they are not mandated by the standard, but are more logical in that context, for example the list-domain (codelist/thesauri) methods.

Methods related to harvesting management and user/group management are probably the first to be migrated to a dedicated micro service.

So we'll have a landscape of microservices, each having their open-api-document. The UI (or documentation) is probably a good place to contain a list of all open-api-documents in a typical geonetwork setup.

A question I have is if we shouldn't create individual projects for ogcapi, harvest-microservice, user/group management?

[fxprunayre]

A question I have is if we shouldn't create individual projects for ogcapi, harvest-microservice, user/group management?

You mean one github repo ? If you need a new service, just add it in https://github.com/geonetwork/geonetwork-microservices/tree/main/modules/services