CSW GetRecords fails when requesting an outputSchema not supported by a metadata schema

[josegar74]

Describe the bug
CSW GetRecords fails when requesting iso19139 outputSchema when the catalogue contains iso19110 metadata.

To Reproduce
Steps to reproduce the behavior:

1. Load iso19110 and iso19119 metadata.
2. Go to Admin console > Settings > CSW Test and select the request csw-GetRecords | no filter | outputSchema: http://www.isotc211.org/2005/gmd. The following error is returned:

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2.0" xsi:schemaLocation="http://www.opengis.net/ows http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd">
  <ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>java.lang.RuntimeException: org.fao.geonet.csw.common.exceptions.InvalidParameterValueEx: code=InvalidParameterValue, locator=OutputSchema, message=OutputSchema 'gmd' not supported for metadata with '102' (iso19110).
Corresponding XSL transformation 'gmd-summary.xsl' does not exist for this schema.
The record will not be returned in response.</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

Expected behavior

As the metadata has no conversion to iso19139 it is ignored, as it was in previous versions. The rest of the metadata is returned.

[fxprunayre]

As the metadata has no conversion to iso19139 it is ignored, as it was in previous versions. The rest of the metadata is returned

No objection to ignore them as in previous versions, but then some users (and harvesters) are having hard time to explain why CSW response does not contains the correct number of requested records. It can be better:

• for the one requesting to use a proper filter to exclude records eg. documentStandard:iso19139
• or create a dedicated portal to only provides ISO19139 records

in order to have consistent CSW search results without ghost records.

[josegar74]

ok, I'll check to setup a portal filtering the proper records.

The problem I see is that the main csw endpoint then becomes useless if you have iso19110 metadata in your catalogue and request iso19139 output.