Previously the values were converted to UTC. If the timezone defined in the server is Europe/Madrid and the metadata has a creation date '2023-01-01T00:00:00', the index field creationYearForResource had the value 2022

Test case:

1) Create an ISO19139 and add a creation date 2023-01-01T00:00:00.

creation-date

2) In the UI settings replace the Search application facet creationYearForResource with

  "creationYearForResource": {
    "terms": {
      "field": "creationYearForResource",
      "order": {
        "_key": "desc"
      }
    },
    "meta": {
      "collapsed": true
    }
  },

creation-date-facet

3) Go to the search page:

Without the fix:

facet-no-ok

With the fix:

facet-ok

@fxprunayre, instead of extracting the year from the XML content, should we convert the date for these fields, not to UTC, but to the server timezone configured?

With the current change we are not dealing with metadata dates that have a timezone.

Checklist

[X] I have read the contribution guidelines
[X] Pull request provided for main branch, backports managed with label
[ ] Good housekeeping of code, cleaning up comments, tests, and documentation
[X] Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
[X] Clean commit messages, longer verbose messages are encouraged
[ ] API Changes are identified in commit messages
[ ] Testing provided for features or enhancements using automatic tests
[ ] User documentation provided for new features or enhancements in manual
[ ] Build documentation provided for development instructions in README.md files
[ ] Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

geonetwork / core-geonetwork

ISO19139 / ISO19115.3 / Index resource date fields as defined in the metadata. #8365

Checklist