geonetwork / geonetwork/core-geonetwork

how to manage inspire requirements for the use of thesauri in online resource section

Open
#4,368 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question stale
Dominant language
Java
Stars
521
Forks
515
Avg merge
6d 13h
Merged PRs (30d)
19

Description

these days inspire recommends the use of values from thesauri in inspire registry for multiple elements in online resources. currently the fields in onlineresource panel are hardcoded and it is not possible to introduce these recommended values. I see 3 options to improve this:

  • Do not use the online resource panel to add online resources, in stead add online resources inline with full control to define proper field types for the elements
  • Use the extension mechanism to redefine the online resource panel to match the inspire expectation
  • Use form post processing to update the xml in an automated way in accordance to recommendations

Concretely, INSPIRE recommends to use following thesaurus values in onlineresource section:

Protocol has 2 additional challenges

  • values need to be selectable from 2 different thesauri (or merge both thesauri to a single)
  • geonetwork has hardcoded links between protocol values and certain functionality (add-to-map, etc). Likely the use of this thesaurus will break these links.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current online resource panel and the extension mechanism discussed in issue #3720. Compare the existing XML output with the listed INSPIRE thesaurus requirements, then investigate the hardcoded protocol links and determine which of the three proposed approaches can preserve the related functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, xml
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.