-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ATOM download service #18
Comments
Some more instructions: |
As a reference: https://en.wikipedia.org/wiki/Atom_(Web_standard) |
Some examples of current deployment ISO record: OpenSearch endpoint: Atom record (internal mode): |
More references on OGC OpenSearch extensions: https://www.ogc.org/standards/opensearchgeo |
Folder created to store the custom atom files: |
Testing the atom/opensearch functionality of GeonetworkSteps:
TG Requirement 43: OpenSearch description document for the tested service: response: Try to get the dataset using the template from the OpenSearch response (Get Spatial Dataset Url): response: I notice that the attribute inspire_dls:crs is not set in the service atom feed, like the other two (inspire_dls:spatial_dataset_identifier_code and inspire_dls:spatial_dataset_identifier_namespace). I checked the inspire_dls xsd here and I see that this attribute is Unfortunately, the get spatial dataset operation, using the above url does not work. And, closing, the attribute “type” of the above Get Spatial Dataset Url, is empty and I do not know how to provide a value for this also. • OpenSearch Description / Describe Spatial Dataset Operation Try to get the description of the dataset using the template in red bold (Describe Spatial Dataset Url): response: • OpenSearch Description / Query example for each dataset • OpenSearch Description / URI to itself The relevant Url |
After the insertion of the port number in Admin console > Settings (port number=80), the test "OpesearchDescription > URI to itself" passed succesfully. The "Get Spatial Dataset Operation" and "Describe Spatial Dataset Operation" still fail though. The issue is reported upstream here geonetwork/core-geonetwork#6086 |
No description provided.
The text was updated successfully, but these errors were encountered: