geonetwork / geonetwork/core-geonetwork
xlink metadata contact does not sync
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 521
- Forks
- 515
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 19
Description
Describe the bug
When I do modify contacts via geonetwork does not trigger indexation of the metadata associated.
To Reproduce
Steps to reproduce the behavior:
- Activate xlink in parameters of geonetwork
- Activate the xlink in the config-editor.xml of the schema (as proposed in here https://github.com/geonetwork/core-geonetwork/pull/8701 )
- Create a subtemplate contact
- Create a metadata linking to this subtemplate contact
- Check if the subtemplate contact is well-connected to the metadata (in "manage directory"), it is
- Update the subtemplate contact info
- Check the xml format of the metadata, the subtemplate contact is up-to-date
- Check the metadata via normal interface, the subtemplate contact is not up-to-date
- run indexation of the metadata via admin console tool / or open metadata editor (without saving) and close it
- The metadata is now up-to-date with the subtemplate contact modification
Expected behavior
Contact is up-to-date without action from the administrator.
Desktop (please complete the following information):
- GeoNetwork Version 4.2.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the xlink contact workflow using the parameters, schema config-editor.xml, subtemplate contact, metadata editor, and admin console indexation tool. Compare the metadata XML with what the normal interface and index show after updating the contact. Done means the indexed metadata reflects the contact change without manual reindexing or opening and closing the editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100