Changes between Version 20 and Version 21 of interop_matrix


Ignore:
Timestamp:
Jun 30, 2011, 12:45:41 AM (13 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • interop_matrix

    v20 v21  
    55||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). ||
    66||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 &apos;original&apos; 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. ||
     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 &apos;original&apos; 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: