Indexing: every ISO19139 record is typed resourceType=dataset regardless of hierarchyLevel

Every ISO19139 record is indexed as resourceType: dataset, whatever its hierarchyLevel declares. Services, series and interactive maps all come back as datasets, so any client filtering or faceting on resourceType sees a catalogue made entirely of datasets.

Reproduction

Index any ISO19139 record whose gmd:hierarchyLevel is something other than dataset, for example service. The indexed document has resourceType: ["dataset"] while cl_hierarchyLevel correctly holds service.

On a 30-record ISO19139 collection here:

The resourceType facet therefore reports dataset (28) and nothing else, on a catalogue that holds 12 services, 3 series and a map.

Cause

index-resourceType in src/modules/indexing/src/main/resources/indexing/xslt/iso-utility.xsl:

<xsl:variable name="isDataset" as="xs:boolean"
              select="
                  count(*:metadataScope[*/*:resourceScope/*/@codeListValue = 'dataset']) > 0 or
                  count(*:hierarchyLevel[*/@codeListValue='dataset']) > 0 or
                  count(*:metadataScope) = 0"/>

The third clause is the "no scope declared means dataset" fallback. metadataScope is the ISO19115-3 element name. An ISO19139 record declares its scope in hierarchyLevel and never has a metadataScope, so for every ISO19139 record that clause is true, $isDataset is true, and the xsl:choose below returns dataset before it can reach the branch that reads the declared scope.

The second clause remembers to check hierarchyLevel. The fallback does not.

GN4 gets this right. In schemas/iso19139/src/main/plugin/iso19139/index-fields/index.xsl the same fallback reads:

count(gmd:hierarchyLevel[gmd:MD_ScopeCode/@codeListValue='dataset']) > 0 or
count(gmd:hierarchyLevel) = 0

Possibly related: $isService is computed just below $isDataset and is never used in the xsl:choose.

Suggested fix

Make the fallback require both scope elements to be absent:

(count(*:metadataScope) = 0 and count(*:hierarchyLevel) = 0)

Impact

resourceType is a queryable and a facet in OGC API - Records, so a Resource Type filter built on it silently collapses to a single value on any ISO19139 catalogue. Reading cl_hierarchyLevel instead works as a client-side workaround, but that field is a codelist rather than the documented type field.