metadata101 / iso19139.nl.geografie.2.0.0 Goto Github PK

View Code? Open in Web Editor NEW

0.0 17.0 5.0 1.02 MB

Dutch profile for datasets v2

License: GNU General Public License v2.0

XSLT 84.15% Groovy 12.23% HTML 3.62%

geonetwork schema-plugin dutch-profile metadata datasets

iso19139.nl.geografie.2.0.0's Introduction

Dutch profile for datasets v2 schema plugin

Dutch profile for datasets v2 (iso19139.nl.geografie.2.0.0).

Installing the plugin

GeoNetwork version to use with this plugin

Use GeoNetwork 4.2.

Adding the plugin to the source code

The best approach is to add the plugin as a submodule:

Use add-schema.sh for automatic deployment:

./add-schema.sh iso19139.nl.geografie.2.0.0 https://github.com/metadata101/iso19139.nl.geografie.2.0.0 4.2.x

Build the application:

mvn clean install -Penv-prod -DskipTests

Once the application is built, the war file contains the schema plugin:
```
cd web
mvn jetty:run -Penv-dev
```

Deploy the profile in an existing installation

After building the application, it's possible to deploy the schema plugin manually in an existing GeoNetwork installation:

Copy the content of the folder schemas/iso19139.nl.geografie.2.0.0/src/main/plugin to INSTALL_DIR/geonetwork/WEB-INF/data/config/schema_plugins/iso19139.nl.geografie.2.0.0
Copy the jar file schemas/iso19139.nl.geografie.2.0.0/target/schema-iso19139.nl.geografie.2.0.0-4.2.2-SNAPSHOT.jar to INSTALL_DIR/geonetwork/WEB-INF/lib.

If there's no changes to the profile Java code or the configuration (config-spring-geonetwork.xml), the jar file is not required to be deployed each time.

Setup xml snippets

The editor uses a snippet-directive for the conformance field which allows to select a snippet from the catalogue, to be introduced at that location. Unzip snippets.zip to a folder, use import (select type 'subtemplate') to import all the files into the catalogue.

Setup thesauri

The editor uses a number of thesauri as pick lists for various fields. These thesauri can be downloaded from the INSPIRE registry and Nationaalgeoregister.nl.

iso19139.nl.geografie.2.0.0's People

Contributors

Watchers

Forkers

juanluisrp geocat pascallike michelgabriel classicvalues

iso19139.nl.geografie.2.0.0's Issues

option to add multiple elements in basic view

Goal of basic view is to have a very simple editor with only required fields, therefore some "add element" buttons are hidden if an instance of an element already exists. For the following elements we would like to see the add button anyway:

keyword (already existing in the new software),
date (so you can add creation and publication date for example)
contact (so we can add multiple contacts).

Hyperlink application profile warning

When I add a WMS or WFS link to the metadata I keep on receiving the warning that I have to add an application profile with an anchor. Even when I add an application profile (which automatically contains an anchor) in the field 'Applicatie profiel' I keep on receiving the warning.

I looked quickly at the code of the file https://github.com/metadata101/iso19139.nl.geografie.2.0.0/blob/3.10.x/src/main/plugin/iso19139.nl.geografie.2.0.0/schematron/schematron-rules-warn-nl-19115-basis.sch and the code in line 61 and 63 seems to be correct.

I also noticed that when you add a new WMS or WFS hyperlink the field 'Omschrijving' (= description) is automatically filled with the layer name. This causes another warning because the field description can only contain 'accesspoint' or 'endpoint': https://docs.geostandaarden.nl/md/mdprofiel-iso19115/#description. I think it would be better to leave the field empty because 'accessPoint' and 'endPoint' are automatically added.

Element description of service automatically takes the title in characterstring instead of the proper description as anchor

According to the INSPIRE rules the element description of the URL should be included as anchor (accessPoint) but the description is included as CharacterString when editing the dataservice through the GUI. The only way to correct this is editing the xml.

        <gmd:MD_DigitalTransferOptions>
           <gmd:onLine xmlns:java="java:org.fao.geonet.util.XslUtil"
                       xmlns:xs="http://www.w3.org/2001/XMLSchema">
              <gmd:CI_OnlineResource>
                 <gmd:linkage>
                    <gmd:URL>https://geodev.XXXXX.nl:7443/wgp/HVB_PWIBON/wms?request=GetCapabilities&amp;service=WFS</gmd:URL>
                 </gmd:linkage>
                 <gmd:protocol>
                    <gmx:Anchor xlink:href="http://www.opengis.net/def/serviceType/ogc/wfs">OGC:WFS</gmx:Anchor>
                 </gmd:protocol>
                 <gmd:applicationProfile>
                    <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download">download</gmx:Anchor>
                 </gmd:applicationProfile>
                 <gmd:name>
                    <gco:CharacterString>XXX_PWIBON:DATATRANSPORT_MANTELBUIS_XXX</gco:CharacterString>
                 </gmd:name>
                 <gmd:description>
                    <gco:CharacterString>DATATRANSPORT_MANTELBUIS_XXX</gco:CharacterString>
                 </gmd:description>
                 <gmd:function>
                    <gmd:CI_OnLineFunctionCode codeList="http://schemas.opengis.net/iso/19139/20060504/resources/Codelist/gmxCodelists.xml#CI_OnLineFunctionCode"
                                               codeListValue="download">download</gmd:CI_OnLineFunctionCode>
                 </gmd:function>
              </gmd:CI_OnlineResource>
           </gmd:onLine>

lengte schematron geeft database fout in geonetwork <3.10

recent zijn enkele schemtrons toegevoegd, door de lengte van de naam geven deze problemen tijdens validatie. In 3.10 zijn deze problemen opgelost door geonetwork/core-geonetwork#4412

workaround is schematron deactiveren via schematron admin (of kortere naam geven)

Some editor issues in 3.8

Contactgegevens organisatie kan niet ingevuld worden
De ingevulde waarde in het veld Contactgegevens dataset/distributeur/metadata – organisatie verdwijnt als het metadata record wordt opgeslagen.

Temporele dekking kan niet ingevuld worden
De ingevulde waarde in het veld Temporele dekking verdwijnt als het metadata record wordt opgeslagen.

Locale kan na toevoegen niet verwijderd worden
Als het veld landinstelling (locale) wordt toegevoegd, kan dit veld niet meer verwijderd worden (zie onderstaande afbeelding).