georss - adding a simple endpoint accessible with a GET request #72
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
the url points at a jar built from https://github.com/geonetwork/geonetwork-microservices/releases/tag/4.2.2 compatible with the geonetwork 4.2.2 shipped in georchestra. when geonetwork/geonetwork-microservices#72 is merged and geonetwork is upgraded to 4.2.3 we can point the georchestra CI at this upstream repo, until now use this self-built jar..
the url points at a jar built from https://github.com/geonetwork/geonetwork-microservices/releases/tag/4.2.2 compatible with the geonetwork 4.2.2 shipped in georchestra. when geonetwork/geonetwork-microservices#72 is merged and geonetwork is upgraded to 4.2.3 we can point the georchestra CI at this upstream repo, until now use this self-built jar..
|
|
||
| /** | ||
| * provides an API endpoint for a GeoRSS endpoint, also sorts the records | ||
| * by changeDate (descending), and limits the results to the first 10. |
There was a problem hiding this comment.
Is this
- https://sextant.ifremer.fr/geonetwork/api/collections/main/items?f=rss or
- https://sextant.ifremer.fr/geonetwork/api/collections/main/items?f=rss&sortby=-dateStamp or
- https://sextant.ifremer.fr/geonetwork/api/collections/main/items?f=rss&sortby=-publicationDateForResource&limit=20
not a simple GET endpoint for RSS ?
There was a problem hiding this comment.
yes, but iirc this was developed before ogc-api-records was able to provide rss (eg around 4.0.x), and i wouldn't be sure it provides the same field mappings. @pmauduit ?
(i agree that those days a standalone rss service doesn't make sense with ogc-api-records doing that and much more)
There was a problem hiding this comment.
for comparison, the service we still use with our 4.0.6 catalog returns this rss content: https://ids.craig.fr/geocat/srv/fre/rss.search
|
|
Afaict, georchestra/geonetwork-microservices@0953b7215 is the only meaningful src commit that was present in the
geor-mainbranch of https://github.com/georchestra/geonetwork-microservices and not present in this upstream repo.cf main...georchestra:geonetwork-microservices:geor-main
having this upstreamed would allow the georchestra project buildbot to start building the searching and ogc-api-records jars from the same repository, instead of providing a badly outdated jar on https://packages.georchestra.org/bot/wars/geonetwork-microservices/
cf georchestra/datadir#271, cc @pmauduit @jahow @fvanderbiest @fgravin