Include point of truth link on the metadata default view in web-app

geonetwork / core-geonetwork

GeoNetwork is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer. It is currently used in numerous Spatial Data Infrastructure initiatives across the world.

http://geonetwork-opensource.org/

GNU General Public License v2.0

426 stars 489 forks source link

Include point of truth link on the metadata default view in web-app #5691

Open craigrose opened 3 years ago

craigrose commented 3 years ago

Is your feature request related to a problem? Please describe.

As the point of truth URL is a essential part of the metadata record it should be easily located on the default view. This is particularly relevant for harvested content as users may not be aware that they need to navigate to full view for the point of truth.

Describe the solution you'd like

Include an easily found point of truth link in the metadata default view.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

pvgenuchten commented 3 years ago

Hi @craigrose, this is an interesting request, I would love to hear from you how you imagine the point-of-truth to be populated. Some conventions I'm aware of, and some suggestions for a coded solution:

Within metadata

iso19115-3 has a section to describe a link to alternate (origin) records in mdb:metadataLinkage
For iso19139 European INSPIRE introduced a convention to populate resource identifier with a gmx:anchor to reference a point of truth

Maintained by GeoNetwork

When a record is harvested from remote, GeoNetwork persists the source of that record, In case of CSW, the getrecordbyid request for that record can be used as point of truth, point of thuth will only be able to navigate to the direct parent, not the original source.

Your pull request seems to focus on the first case?

craigrose commented 3 years ago

Hi - thanks for the interest.

I did indeed dev this from a iso19115-3 perspective. We intend on maintaining the source of the value within metadata. The intention is that indexed field is included in the schema plugin configuration. If I understand correctly, as such, this allows for a different identifier to be used for different schemas.

eg something like

    <xsl:template mode="index" match="mdb:metadataLinkage[1]/cit:CI_OnlineResource">
        <Field name="metadataLinkage" string="{cit:linkage/*/text()}" store="true" index="true"/>
    </xsl:template>

This is to produce consistent results with the Full View of the record.

Using the "maintained by GeoNetwork" approach seems limiting in that it defines a point of truth as the direct parent rather than original point of truth specified in the record, which is our intention.