georss - adding a simple endpoint accessible with a GET request #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Kudos, SonarCloud Quality Gate passed!
|
landryb
added a commit
to georchestra/ansible
that referenced
this pull request
Mar 30, 2023
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..
landryb
added a commit
to georchestra/ansible
that referenced
this pull request
Mar 30, 2023
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..
fxprunayre
reviewed
Apr 26, 2023
|
|
||
| /** | ||
| * 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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