[GeoNetwork-devel] CSW harvester typeNames parameter

GeoNetwork GeoNetwork Developer
,
1

Hi

I got a report from a customer that the CSW harvester can’t harvest one of his servers, due to send in typeNames a list of values (all the values reported in the capabilities by the remote server) and the server fails. Changing the request to send only 1 typeName value seem working fine.

Although in the OGC specs the data type for typeNames is a list, the usage seem that mandates one. See this:

In OGC 07-006:

typeNames

Data type and value:

List of Character String, comma separated

Unordered List of object types implicated in the query

Optionality and use:

One (Mandatory)

In OGC 07-045 (ISO API Profile):

typeNames

Data type and value:

List of Character String, comma separated

Used to specify which entities, from the information model of the catalogue, shall be queried.

Optionality and use:

Mandatory: Must support o****ne of “csw:Record” or “gmd:MD_Metadata” in a query. Default value is “csw:Record”.

OGC specs are sometimes not very clear, but in this case seem the implementation in GeoNetwork is wrong and have use the generic data type instead the specific restriction defined in the spec? What are your thoughts?

I would like to change the code according to the spec, but want to check if I’m missing something?

Thanks and regards,
Jose García

–

GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer and GeoNetwork. Visit http://geocat.net for details.

Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net

2

Hi Jose,

···

2014-02-07 9:52 GMT+01:00 Jose Garcia <jose.garcia@anonymised.com.437…>:

Hi

I got a report from a customer that the CSW harvester can’t harvest one of his servers, due to send in typeNames a list of values (all the values reported in the capabilities by the remote server) and the server fails. Changing the request to send only 1 typeName value seem working fine.

I think having multiple typename in the typenames parameter is correct but maybe we should add to the harvester config the list of typenames to query on (extracted from the capabilities) ? And maybe set it to null by default, in order to use csw:Record by default which supported by most of the CSW servers.

And then properly handle it on the CSW server here https://github.com/geonetwork/core-geonetwork/blob/develop/csw-server/src/main/java/org/fao/geonet/kernel/csw/services/getrecords/CatalogSearcher.java#L176

Cheers.

Francois

Although in the OGC specs the data type for typeNames is a list, the usage seem that mandates one. See this:

In OGC 07-006:

typeNames

Data type and value:

List of Character String, comma separated

Unordered List of object types implicated in the query

Optionality and use:

One (Mandatory)

In OGC 07-045 (ISO API Profile):

typeNames

Data type and value:

List of Character String, comma separated

Used to specify which entities, from the information model of the catalogue, shall be queried.

Optionality and use:

Mandatory: Must support o****ne of “csw:Record” or “gmd:MD_Metadata” in a query. Default value is “csw:Record”.

OGC specs are sometimes not very clear, but in this case seem the implementation in GeoNetwork is wrong and have use the generic data type instead the specific restriction defined in the spec? What are your thoughts?

I would like to change the code according to the spec, but want to check if I’m missing something?

Thanks and regards,
Jose García

–

GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer and GeoNetwork. Visit http://geocat.net for details.

Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net

Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk

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