Changes between Version 24 and Version 25 of interop_matrix


Ignore:
Timestamp:
Nov 7, 2013, 9:33:12 AM (10 years ago)
Author:
ticheler
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • interop_matrix

    v24 v25  
    22
    33||'''Server'''||'''GN version and build'''||'''Harvesting'''||'''Harvester URL'''||'''Client'''||'''Does harvest work?'''||'''Error'''||'''Protocol & version'''||'''Comments'''||
    4 ||ESRI !GeoPortal 1.1.0.41||2.7 Build 7809||CSW||http://localhost:5555/geoportal/csw?request=GetCapabilities&service=CSW&version=2.0.2||GeoNetwork||Yes - but records without gmd: prefix will be rejected because of a bug in handling of namespaces and prefixes - the bug is #546 and a fix has already been developed for 2.7 ||||CSW 2.0.2||ESRI Geoportal installed on localhost with ISO19115 records. '''NOTE:''' If using 'Free text' in search criteria, specify search term with '%' wildcard characters eg. %ESRI% would search for records which have the string ESRI anywhere in their content.||
    5 ||GeoNetwork||2.7 Build 7809||CSW||http://localhost:8080/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2||ESRI !GeoPortal 1.1.0.41||Yes||||CSW 2.0.2||ESRI Geoportal harvesting from GeoNetwork using CSW synchronization with Profile 'GeoNetwork CSW 2.0.2 APISO' selected. '''NOTE:''' '''(1)''' Set the CSW Server Configuration values in Administration->CSW Server Configuration on GeoNetwork before attempting synchronization otherwise you will receive funky error messages in the ESRI Geoportal Add screen about 'title' not set etc. '''(2)''' Records must validate against schemas otherwise they will be rejected by the ESRI Geoportal (code says something about isDraft but not sure yet how to tell Geoportal to harvest them as draft/unfinished). ||
    6 ||GeoNetwork||2.7 Build 7809||OAIPMH||http://localhost:8080/geonetwork/srv/en/oaipmh||ESRI !GeoPortal 1.1.0.41||Yes||||OAIPMH 2.0||ESRI Geoportal harvesting from GeoNetwork using OAIPMH synchronization with prefix iso19139 and set 'datasets' '''NOTE''' Records must validate against schemas otherwise they will be rejected by the ESRI Geoportal.||
    7 || ESRI Geoportal Extension 9.3.1 || 2.7 Build 7939 || CSW || http://gis.ncdc.noaa.gov/geoportal/csw/discovery?Request=GetCapabilities&Service=CSW&Version=2.0.2 || GeoNetwork || No || exceptionCode="!InvalidParameterValue" locator="!ElementSetName" <!ExceptionText>!ElementSetName is not valid for 'original' outputScheme</!ExceptionText> || CSW 2.0.2 || This response, which is generated when GeoNetwork sends a !GetRecordById request, seems to me to be a trifle odd as both the outputSchema and the elementSetName used by GeoNetwork are advertised in the Geoportal's !GetCapabilities statement in the !GetRecordById operation section! Fiddling with the !GetRecordById request outside of GeoNetwork, I can get the record if I drop the outputSchema, and elementSetName works just fine with brief and summary as well as full. Even more odd is that 'original' is also listed as an outputSchema and when used as an outputSchema it works correctly by returning a dc metadata record. ||
     4||ESRI !GeoPortal 1.1.0.41||2.7 Build 7809||CSW||http://localhost:5555/geoportal/csw?request=GetCapabilities&service=CSW&version=2.0.2||!GeoNetwork||Yes - but records without gmd: prefix will be rejected because of a bug in handling of namespaces and prefixes - the bug is #546 and a fix has already been developed for 2.7 ||||CSW 2.0.2||ESRI Geoportal installed on localhost with ISO19115 records. '''NOTE:''' If using 'Free text' in search criteria, specify search term with '%' wildcard characters eg. %ESRI% would search for records which have the string ESRI anywhere in their content.||
     5||!GeoNetwork||2.7 Build 7809||CSW||http://localhost:8080/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2||ESRI !GeoPortal 1.1.0.41||Yes||||CSW 2.0.2||ESRI Geoportal harvesting from !GeoNetwork using CSW synchronization with Profile '!GeoNetwork CSW 2.0.2 APISO' selected. '''NOTE:''' '''(1)''' Set the CSW Server Configuration values in Administration->CSW Server Configuration on !GeoNetwork before attempting synchronization otherwise you will receive funky error messages in the ESRI Geoportal Add screen about 'title' not set etc. '''(2)''' Records must validate against schemas otherwise they will be rejected by the ESRI Geoportal (code says something about isDraft but not sure yet how to tell Geoportal to harvest them as draft/unfinished). ||
     6||!GeoNetwork||2.7 Build 7809||OAIPMH||http://localhost:8080/geonetwork/srv/en/oaipmh||ESRI !GeoPortal 1.1.0.41||Yes||||OAIPMH 2.0||ESRI Geoportal harvesting from !GeoNetwork using OAIPMH synchronization with prefix iso19139 and set 'datasets' '''NOTE''' Records must validate against schemas otherwise they will be rejected by the ESRI Geoportal.||
     7|| ESRI Geoportal Extension 9.3.1 || 2.7 Build 7939 || CSW || http://gis.ncdc.noaa.gov/geoportal/csw/discovery?Request=GetCapabilities&Service=CSW&Version=2.0.2 || !GeoNetwork || No || exceptionCode="!InvalidParameterValue" locator="!ElementSetName" <!ExceptionText>!ElementSetName is not valid for 'original' outputScheme</!ExceptionText> || CSW 2.0.2 || This response, which is generated when !GeoNetwork sends a !GetRecordById request, seems to me to be a trifle odd as both the outputSchema and the elementSetName used by !GeoNetwork are advertised in the Geoportal's !GetCapabilities statement in the !GetRecordById operation section! Fiddling with the !GetRecordById request outside of !GeoNetwork, I can get the record if I drop the outputSchema, and elementSetName works just fine with brief and summary as well as full. Even more odd is that 'original' is also listed as an outputSchema and when used as an outputSchema it works correctly by returning a dc metadata record. ||
    88
    99Older tests:
     
    2222||Demo deegree||2.2 build r1291||CSW||http://demo.deegree.org/deegree-csw/services?REQUEST=GetCapabilities&service=CSW||deegree 2.1||No||!GeoNetwork: "Raised exception when searching"||2.0.0||        ||
    2323||AWCUBED||2.2 build r1291||CSW||http://server.awcubed.com:8080/geonetwork/srv/en/csw?service=CSW&request=GetCapabilities||!GeoNetwork 2.2||Yes|| ||2.0.2||     ||
    24 ||AWCUBED||2.2 build r1291||!GeoNetwork||host: server.awcubed.com , port: 8080 , servlet: geonetwork||!GeoNetwork 2.2||Yes|| || ||Direct !!GeoNetwork harvesting||
     24||AWCUBED||2.2 build r1291||!GeoNetwork||host: server.awcubed.com , port: 8080 , servlet: geonetwork||!GeoNetwork 2.2||Yes|| || ||Direct !GeoNetwork harvesting||
    2525||NASA||2.2 build r1291||CSW||http://esg.gsfc.nasa.gov/wes/serviceManagerCSW/csw?request=GetCapabilities&version=2.0.2||Compusult||     No||!GeoNetwork: "Raised exception when searching"||2.0.2||     ||
    2626||INSPIRE||2.2 build r1291||CSW||http://geoportal.jrc.it/csw/CSWStartup?service=CSW&request=GetCapabilities||!ConTerra||No||!GeoNetwork: "Raised exception when searching"||2.0.0||     ||