geonetwork / geonetwork/core-geonetwork

Issue validating multilingual records from the contribute tab in GeoNetwork 4.2

Open
#8,080 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
521
Forks
514
Avg merge
6d 13h
Merged PRs (30d)
19

Description

**Describe the bug**
When validating a multilingual record from the contribute tab, there are numerous validation errors:
`The 'gmd:LocalisedCharacterString' element has no child elements.`
This can be seen in ISO19139 with the multilingual template record. Validating a record individually from its edit view does not trigger the same errors.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'metadata and templates' and load the template records for ISO19139
2. In the contribute tab select the `Template for Vector data in ISO19139 (multilingual)` record
3. Validate it
4. See the errors in the validation report

**Expected behavior**
Validation from the contribute tab should not trigger these errors

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the validation from the contribute tab using the ISO19139 multilingual template record, then compare its validation report with validation from the record's edit view. Trace the two validation entry points and identify why only the contribute-tab path reports LocalisedCharacterString errors. Done means both paths validate the record without these errors.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.