forked from GeoNode/geonode
-
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
Feature: implement use_constraints with restrictioncodes #112
Labels
API
changes to rest API
feature
Forms
changes to metadata forms
Metadata
MetadataXML
changes to the metadata XML
Comments
mwallschlaeger
added
feature
API
changes to rest API
Forms
changes to metadata forms
MetadataXML
changes to the metadata XML
Metadata
labels
Jun 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
API
changes to rest API
feature
Forms
changes to metadata forms
Metadata
MetadataXML
changes to the metadata XML
Feature Description
COMPLICATED TO DESCRIBE, ASK @mwallschlaeger for details
We're decided to have a two part approach for constraints:
.
Upstream geonode implements this with
Restrictions
andOther constraints
like:This we can use to impl. 2. as it is exactly what we need.
for 1. we need to reimplement the field use_constraints (which is in zalf/geonode, but not in the way we need it) to be a free text field, and another field use_constraints_restrictions which holds the restriction codes applied to use_constraints so they can also be written to the xml like:
tasks todo:
geonode.base.models.ResourceBase
and described wellrestrction_codes
, use_constraints_restrictions and other_constraints_restrictions, best impliment both asonetomany
, they can share the same database table in the backendgeonode.catalogue.templates.full_metadata.xml
pycsw
local_mapping
need to take placePART OF #9
The text was updated successfully, but these errors were encountered: