[GeoNetwork-devel] applying XSLT

GeoNetwork GeoNetwork Developer
1

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

···

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com…

2

Hi,

Not sure if you’re running from source code or not, but you could first check that XSL caching is off see http://osgeo-org.1560.x6.nabble.com/Remove-xsl-cache-td5083228.html.

HTH.

Francois

···

2016-02-24 13:54 GMT+01:00 Dragan Divjak <dragan.divjak@…842…>:

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

3

Dear Francois,
I already turned the caching off, but that didn’t helped neither.
To elaborate issue more specific - I’m not running it from source code. I just edited XSL files in installation folder on my local machine where I’m doing tests at the moment.
cheers,
Dragan

···

On Wed, Feb 24, 2016 at 2:00 PM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi,

Not sure if you’re running from source code or not, but you could first check that XSL caching is off see http://osgeo-org.1560.x6.nabble.com/Remove-xsl-cache-td5083228.html.

HTH.

Francois

–

2016-02-24 13:54 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com>:

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com…842…

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

4

Hi

···

2016-02-25 9:52 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com…>:

Dear Francois,
I already turned the caching off, but that didn’t helped neither.

To elaborate issue more specific - I’m not running it from source code. I just edited XSL files in installation folder on my local machine where I’m doing tests at the moment.

In that case, you’ve to update files in the iso19139 schema directory (and not in xsl/conversion)
https://github.com/geonetwork/core-geonetwork/tree/develop/schemas/iso19139/src/main/plugin/iso19139/convert/OGCWxSGetCapabilitiesto19119

HTH.

Francois

cheers,
Dragan

On Wed, Feb 24, 2016 at 2:00 PM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi,

Not sure if you’re running from source code or not, but you could first check that XSL caching is off see http://osgeo-org.1560.x6.nabble.com/Remove-xsl-cache-td5083228.html.

HTH.

Francois

–

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

2016-02-24 13:54 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com…>:

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

5

Hi again,
still not making progress :frowning:
Here is what I’ve done:

  1. In folder \web\geonetwork\WEB-INF\data\config\schema_plugins\iso19139\convert\OGCWxSGetCapabilitiesto19119 i edit OGCWxSGetCapabilities-to-19119.xsl
  2. Only thing I edited was the lineage element. Now it look like this:

    <LI_Lineage>

    gco:CharacterStringThis dataset was created for Danube management plan</gco:CharacterString>

    </LI_Lineage>
However, harvested MD record still got same Lineage content:

-gmd:lineage
-gmd:LI_Lineage

-<gmd:statement gco:nilReason=“missing”>

gco:CharacterString/

</gmd:statement>

</gmd:LI_Lineage>

</gmd:lineage>

···

On Thu, Feb 25, 2016 at 9:56 AM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi

–

2016-02-25 9:52 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com>:

Dear Francois,
I already turned the caching off, but that didn’t helped neither.

To elaborate issue more specific - I’m not running it from source code. I just edited XSL files in installation folder on my local machine where I’m doing tests at the moment.

In that case, you’ve to update files in the iso19139 schema directory (and not in xsl/conversion)
https://github.com/geonetwork/core-geonetwork/tree/develop/schemas/iso19139/src/main/plugin/iso19139/convert/OGCWxSGetCapabilitiesto19119

HTH.

Francois

cheers,
Dragan

On Wed, Feb 24, 2016 at 2:00 PM, Francois Prunayre <fx.prunayre@anonymised.com…> wrote:

Hi,

Not sure if you’re running from source code or not, but you could first check that XSL caching is off see http://osgeo-org.1560.x6.nabble.com/Remove-xsl-cache-td5083228.html.

HTH.

Francois

–

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

2016-02-24 13:54 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com…842…>:

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

6

Hi Dragan,

···

2016-02-25 14:36 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com>:

Hi again,
still not making progress :frowning:

Odd.

Here is what I’ve done:

  1. In folder \web\geonetwork\WEB-INF\data\config\schema_plugins\iso19139\convert\OGCWxSGetCapabilitiesto19119 i edit OGCWxSGetCapabilities-to-19119.xsl
  2. Only thing I edited was the lineage element. Now it look like this:

    <LI_Lineage>

    gco:CharacterStringThis dataset was created for Danube management plan</gco:CharacterString>

    </LI_Lineage>
However, harvested MD record still got same Lineage content:

-gmd:lineage
-gmd:LI_Lineage

-<gmd:statement gco:nilReason=“missing”>

gco:CharacterString/

</gmd:statement>

</gmd:LI_Lineage>

</gmd:lineage>

It works fine here. You should probably do the change for both the service metadata records https://github.com/geonetwork/core-geonetwork/blob/develop/schemas/iso19139/src/main/plugin/iso19139/convert/OGCWxSGetCapabilitiesto19119/OGCWxSGetCapabilities-to-19119.xsl#L354
and for dataset records
https://github.com/geonetwork/core-geonetwork/blob/develop/schemas/iso19139/src/main/plugin/iso19139/convert/OGCWxSGetCapabilitiesto19119/OGCWxSGetCapabilitiesLayer-to-19139.xsl#L328

I don’t see any others reasons.

HTH

Francois

On Thu, Feb 25, 2016 at 9:56 AM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi

–

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

2016-02-25 9:52 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com>:

Dear Francois,
I already turned the caching off, but that didn’t helped neither.

To elaborate issue more specific - I’m not running it from source code. I just edited XSL files in installation folder on my local machine where I’m doing tests at the moment.

In that case, you’ve to update files in the iso19139 schema directory (and not in xsl/conversion)
https://github.com/geonetwork/core-geonetwork/tree/develop/schemas/iso19139/src/main/plugin/iso19139/convert/OGCWxSGetCapabilitiesto19119

HTH.

Francois

cheers,
Dragan

On Wed, Feb 24, 2016 at 2:00 PM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi,

Not sure if you’re running from source code or not, but you could first check that XSL caching is off see http://osgeo-org.1560.x6.nabble.com/Remove-xsl-cache-td5083228.html.

HTH.

Francois

–

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

2016-02-24 13:54 GMT+01:00 Dragan Divjak <dragan.divjak@anonymised.com>:

Hi list,
I am having problem with applying custom XSL transformation on harvested records. I added .xsl file in:
\web\geonetwork\xsl\conversion\import
folder and I’m able to choose it under “XSL transformation to apply” option when setting up a harvester. However, nothing happens to harvested MD files.
I used existing “OGCWMSGetCapabilities-to-ISO19119_ISO19139.xsl” and corresponding …\OGCWxSGetCapabilitiesto19119\OGCWxSGetCapabilities-to-19119.xsl file
It seems whatever changes I make to these files is not affecting harvester.

Any help is more than welcome.
cheers,

Mr. Sc. Dragan Divjak, dipl. ing. geod. et geoinf.
External Consultant
European Commission, DG Joint Research Centre
Institute for Environment and Sustainability
Digital Earth and Reference Data Unit, T.P. 262
Via E. Fermi, 2749.
I-21027 Ispra (VA)
Italy
e-mail: dragan.divjak@anonymised.com

Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork