[GeoNetwork-users] GeoNetwork v2.10.3 - auto-transform xml from v2.4.3 or v2.6 into new template?

Hi,

I have an up and running GeoNetwork v2.10.3 catalogue with an "inserted"
INSPIRE metadata schema based on iso19139. I have an older GeoNetwork v2.4.3
catalogue with iso19139 metadata xml. I would like to transform the metadata
in the older iso19139 format into the newer iso19139 format.

Has anyone in the GeoNetwork Community had experience in having to update
xml structure from one schema template to another using transform tools? I
would like to avoid having to re-generate metadata content from scratch in
the new valid template?

Any support from the GeoNetwork Community most welcome?

Kind regards, Trevor

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoNetwork-v2-10-3-auto-transform-xml-from-v2-4-3-or-v2-6-into-new-template-tp5153004.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

Hi Trevor

In the iso19139 schema folder there's a subfolder process:

geonetwork/WEB-INF/data/config/schema_plugins/iso19139/process

You can add a xsl that manages the conversion (see in the folder, there're
already some inspire processes).

I think in 2.10 there's no UI to execute these processes, but you can
manage like this:

1) Login as Administrator

2) In the search UI select all the metadata records to be processed.

2) Lets assume that your xsl file is named inspire-update.xsl:

http://SERVERNAME/geonetwork/srv/eng/metadata.processing?process=inspire-update

If the xsl process requires parameters:

http://SERVERNAME/geonetwork/srv/eng/metadata.processing?process=inspire-update&param1=value1&
..

Regards,
Jose García

On Thu, Jul 24, 2014 at 11:27 AM, talcorn <trevor.alcorn@anonymised.com> wrote:

Hi,

I have an up and running GeoNetwork v2.10.3 catalogue with an "inserted"
INSPIRE metadata schema based on iso19139. I have an older GeoNetwork
v2.4.3
catalogue with iso19139 metadata xml. I would like to transform the
metadata
in the older iso19139 format into the newer iso19139 format.

Has anyone in the GeoNetwork Community had experience in having to update
xml structure from one schema template to another using transform tools? I
would like to avoid having to re-generate metadata content from scratch in
the new valid template?

Any support from the GeoNetwork Community most welcome?

Kind regards, Trevor

--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/GeoNetwork-v2-10-3-auto-transform-xml-from-v2-4-3-or-v2-6-into-new-template-tp5153004.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--

* GeoCat Bridge for ArcGIS allows instant publishing of data and metadata
on GeoServer and GeoNetwork. Visit http://geocat.net
<http://geocat.net/&gt; for details. _________________________Jose
GarcíaGeoCat bvVeenderweg 13 6721 WD BennekomThe
Netherlandshttp://GeoCat.net/> *