-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
GNIP 83 - ResourceBase for metadata-only resources #7057
Comments
please see #6744 and #6876 which discussed similar concepts. I do not understand why metadata only Resources should not be part of the search system. Furthermore, I do not understand the use-case:
Currently, a dataset is uploaded and stored as 'layer' which itself is:
So what exactly is meant by 'details the WMS, WFS and WCS services'? |
A layer creates an ISO19115 metadata belonging to the "dataset" hierarchy, which documents data. A service metadata is an ISO19115 metadata which describes the service in its entirety. So, if I have a CSW catalog, I want to query, for instance, for "view services" to obtain the available WMS endpoints, or for "download services" to get WFS and WCS endpoints, which are not the endpoints provided by the layers metadata, but information about the services themselves. INSPIRE requires that a catalog should provide service metadata for an organization. If GeoNode can not provide them, then GeoNode can only be used as a slave catalog by some other high level catalog that can include such extra metadata. With this GNIP we can remove the use of other catalogs in the architecture. |
+1 |
Just a little sidenote and house-keeping:
I think this is not a big deal and I am happy this GNIP is worked upon and it is almost finished. But we as PSC (@t-book @afabiani @giohappy @francbartoli @simod) should keep an eye on the voting and remind the other members to give their +1/0/-1 ! |
Thanks for reminding @gannebamm +1 |
GNIP 83 - ResourceBase for metadata-only resources
Overview
Flag
ResourceBase
instances in order not to be displayed in the GUI, but only available through CSW.Proposed By
Assigned to Release
This proposal is for GeoNode .
State
Motivation
With this kind of "hidden" ResourceBase, our underlying pyCSW can be decoupled from the data handled in GeoNode/GeoServer, and regain a bit of the functionalities lost when using the internal pyCSW (the only one currenlty maintained) wrt external catalogs.
A good use case is the publishing of service metadata documents that details the WMS, WFS and WCS services offered by our GeoNode/GeoServer instance.
Proposal
The proposal is about adding a new boolean field
ResourceBase.metadata_only
, defaulting to false.The queries used to present resources on screen should exclude the ResourceBase records having
metadata_only=True
.The CSW endpoint should be able to handle such records, so no changes are needed on that side.
Please note that it's up to future development or external modules to add metadata only records.
Backwards Compatibility
The DB migration process will set the new fields to the default value, so existing data will all be visibile on GUI.
If no external logic is added which creates metadata only records, no changes will be visibile on the GeoNode instance.
External clients that use a generic API that returns all of the ResourceBase fields should be aware of the new attribute.
Anyway the presence of records with the metadata_only attribute set will be well-known in the GeoNode setup (since by default nothing will add such records), so the system architects shall consider how the metadata_only records will be used in the specific context.
External clients that use CSW should be aware that they will get all of the records. Anyway the same recommendations in previous paragraph applies here as well.
Future evolution
We're developing a contrib app that allows the admin to add service metadata to the catalog.
Feedback
Update this section with relevant feedbacks, if any.
Voting
Project Steering Committee:
Links
Remove unused links below.
The text was updated successfully, but these errors were encountered: