[GeoNetwork-devel] Related metadata selection - 2.6.0-RC0

I’ve a similar problem with the CSW-Interface.

The name of the field in the Lucene-Index has changed from 2.4.3 → 2.6.0 RC1 parentId → parentUuid

Please fix the mapping in the config-csw.xml to the new fieldname.
<parameter name=“ParentIdentifier” field="parentId"type=“SupportedISOQueryables”>

Kind regards,
Juergen

James Rapaport schrieb:

···
-- 

Jürgen Weichand
Landesamt für Vermessung und Geoinformation
- Betrieb GeodatenOnline, Schnittstellen zu Spezialanwendungen  -
Alexandrastrasse 4
D-80538 München

Mail:   [Juergen.Weichand@anonymised.com](mailto:Juergen.Weichand@anonymised.com)
Web:    [http://www.geodaten.bayern.de](http://www.geodaten.bayern.de)

Thanks Jürgen, fixed in trunk.

The issue reported by James, is another problem I think.

2010/8/6 Jürgen Weichand <juergen.weichand@anonymised.com>:

I've a similar problem with the CSW-Interface.

The name of the field in the Lucene-Index has changed from 2.4.3 --> 2.6.0
RC1 parentId --> parentUuid

Please fix the mapping in the config-csw.xml to the new fieldname.
<parameter name="ParentIdentifier"
field="parentId"type="SupportedISOQueryables">

Kind regards,
Juergen

James Rapaport schrieb:

I've been trying out the Related metadata selection / parentIdentifier
functionality in 2.6.0-RC0. When searching using the Related metadata
selection dialog, it seems that metadata instances based on sample templates
(e.g. Template for Raster data in ISO 19139) are found but metadata
instances based on my bespoke template (also ISO 19139) are not found.

The difference between the metadata instances, based on the two templates,
is large but I've checked that the metadata instance that was based on my
template is valid (both schema and Schematron) using an application outside
GeoNetwork. I can't see any other obvious differences outside the metadata
such as their privileges and so on.

When running parentIdentifier search for selection a default filter is
applied to search only for dataset
which is maybe not a good idea as parents may be a serie for example.
If you change your hierarchy level you should found your metadata
records.

I'll check that and fix the default filter.

Cheers.

Francois

The GeoNetwork instance is running on Tomcat 6 using PostgreSQL 8.4. I
compiled it from source using Eclipse Helios.

I would certainly find this particular functionality useful so I'd be
grateful if this issue could be resolved - or if anyone can suggest if I'm
going wrong somewhere.

Kind regards,

James

________________________________
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm

________________________________
_______________________________________________
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

--

Jürgen Weichand
Landesamt für Vermessung und Geoinformation
- Betrieb GeodatenOnline, Schnittstellen zu Spezialanwendungen -
Alexandrastrasse 4
D-80538 München

Mail: Juergen.Weichand@anonymised.com
Web: http://www.geodaten.bayern.de

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
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

Thanks Francois - that was exactly the problem. My metadata has a hierarchy level of model. I wondered whether hierarchy level was the cause - but only tested the theory by changing it to series...

Cheers,

James
________________________________________
From: Francois Prunayre [fx.prunayre@anonymised.com]
Sent: 06 August 2010 09:16
To: Jürgen Weichand
Cc: James Rapaport; jeroen.ticheler@anonymised.com; geonetwork-devel@anonymised.comeforge.net
Subject: Re: [GeoNetwork-devel] Related metadata selection - 2.6.0-RC0

Thanks Jürgen, fixed in trunk.

The issue reported by James, is another problem I think.

2010/8/6 Jürgen Weichand <juergen.weichand@anonymised.com>:

I've a similar problem with the CSW-Interface.

The name of the field in the Lucene-Index has changed from 2.4.3 --> 2.6.0
RC1 parentId --> parentUuid

Please fix the mapping in the config-csw.xml to the new fieldname.
<parameter name="ParentIdentifier"
field="parentId"type="SupportedISOQueryables">

Kind regards,
Juergen

James Rapaport schrieb:

I've been trying out the Related metadata selection / parentIdentifier
functionality in 2.6.0-RC0. When searching using the Related metadata
selection dialog, it seems that metadata instances based on sample templates
(e.g. Template for Raster data in ISO 19139) are found but metadata
instances based on my bespoke template (also ISO 19139) are not found.

The difference between the metadata instances, based on the two templates,
is large but I've checked that the metadata instance that was based on my
template is valid (both schema and Schematron) using an application outside
GeoNetwork. I can't see any other obvious differences outside the metadata
such as their privileges and so on.

When running parentIdentifier search for selection a default filter is
applied to search only for dataset
which is maybe not a good idea as parents may be a serie for example.
If you change your hierarchy level you should found your metadata
records.

I'll check that and fix the default filter.

Cheers.

Francois

The GeoNetwork instance is running on Tomcat 6 using PostgreSQL 8.4. I
compiled it from source using Eclipse Helios.

I would certainly find this particular functionality useful so I'd be
grateful if this issue could be resolved - or if anyone can suggest if I'm
going wrong somewhere.

Kind regards,

James

________________________________
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm

________________________________
_______________________________________________
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

--

Jürgen Weichand
Landesamt für Vermessung und Geoinformation
- Betrieb GeodatenOnline, Schnittstellen zu Spezialanwendungen -
Alexandrastrasse 4
D-80538 München

Mail: Juergen.Weichand@anonymised.com
Web: http://www.geodaten.bayern.de

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
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

2010/8/6 James Rapaport <James.Rapaport@anonymised.com>:

Thanks Francois - that was exactly the problem. My metadata has a hierarchy level of model. I wondered whether hierarchy level was the cause - but only tested the theory by changing it to series...

Ok I will change that to not apply any filters when searching for
parent or when linking metadata to services so user could select any
type of records. Only feature catalogue and service will have a
default filter.

Thanks for testing.

Francois

Cheers,

James
________________________________________
From: Francois Prunayre [fx.prunayre@anonymised.com]
Sent: 06 August 2010 09:16
To: Jürgen Weichand
Cc: James Rapaport; jeroen.ticheler@anonymised.com; geonetwork-devel@anonymised.comrceforge.net
Subject: Re: [GeoNetwork-devel] Related metadata selection - 2.6.0-RC0

Thanks Jürgen, fixed in trunk.

The issue reported by James, is another problem I think.

2010/8/6 Jürgen Weichand <juergen.weichand@anonymised.com>:

I've a similar problem with the CSW-Interface.

The name of the field in the Lucene-Index has changed from 2.4.3 --> 2.6.0
RC1 parentId --> parentUuid

Please fix the mapping in the config-csw.xml to the new fieldname.
<parameter name="ParentIdentifier"
field="parentId"type="SupportedISOQueryables">

Kind regards,
Juergen

James Rapaport schrieb:

I've been trying out the Related metadata selection / parentIdentifier
functionality in 2.6.0-RC0. When searching using the Related metadata
selection dialog, it seems that metadata instances based on sample templates
(e.g. Template for Raster data in ISO 19139) are found but metadata
instances based on my bespoke template (also ISO 19139) are not found.

The difference between the metadata instances, based on the two templates,
is large but I've checked that the metadata instance that was based on my
template is valid (both schema and Schematron) using an application outside
GeoNetwork. I can't see any other obvious differences outside the metadata
such as their privileges and so on.

When running parentIdentifier search for selection a default filter is
applied to search only for dataset
which is maybe not a good idea as parents may be a serie for example.
If you change your hierarchy level you should found your metadata
records.

I'll check that and fix the default filter.

Cheers.

Francois

The GeoNetwork instance is running on Tomcat 6 using PostgreSQL 8.4. I
compiled it from source using Eclipse Helios.

I would certainly find this particular functionality useful so I'd be
grateful if this issue could be resolved - or if anyone can suggest if I'm
going wrong somewhere.

Kind regards,

James

________________________________
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm

________________________________
_______________________________________________
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

--

Jürgen Weichand
Landesamt für Vermessung und Geoinformation
- Betrieb GeodatenOnline, Schnittstellen zu Spezialanwendungen -
Alexandrastrasse 4
D-80538 München

Mail: Juergen.Weichand@anonymised.com
Web: http://www.geodaten.bayern.de

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
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