Upgrade guidance for geonetwork 3 users

[jodygarnett]

Including mitigation guidance for removed services.

This is an action item from PSC meeting documenting the information from #4727 in the user manual.

I personally have questions after writing this documentation, but to stay on topic minimal guidance has been provided.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• 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

[jahow]

Thanks Jody, support for OAI PMH is coming soon with #7583 so we might not need to advertise it as not supported anymore

[jodygarnett]

support for OAI PMH is coming soon with #7583 so we might not need to advertise it as not supported anymore

Thanks @jahow I have updated that page to indicate that there is interested.

[jodygarnett]

All feedback has been addressed.

• changed doc build to --strict to prevent warnings being ignored, they will now break the build
• update instructions - Java 11 is required
• update and install instructions Elasticsearch version (in keeping with GeoNetwork does not support Elasticsearch 8.6.2 version, what versions are supported? #6855)

[geonetworkbuild]

The backport to 4.2.x failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply f3e8b00617... Upgrade guidance for geonetwork 3 users
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

stdout

Auto-merging docs/manual/docs/api/search.md
CONFLICT (content): Merge conflict in docs/manual/docs/api/search.md
Auto-merging docs/manual/docs/install-guide/index.md
Auto-merging docs/manual/mkdocs.yml
Auto-merging docs/manual/pom.xml

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-7644-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick f3e8b006173c16e9a82ba9e7494b8f5cf7a90869,cc3fff572de6364880cf8acd0a1de3aca591a327,37a60589fe92f143406d3c73c18320b3c54a3c7c,9c36491ae875ed3d3d0a82c32907c33997c35c6d,367f21a811677121d3e43447c1feea2f2dcac659,c43d099d9d90338766ef4a8f5e1340d3ae054a6d,bd9b28de5ba5afe628790bff7300907f3a4f6fd9
# Push it to GitHub
git push --set-upstream origin backport-7644-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x

Then, create a pull request where the base branch is 4.2.x and the compare/head branch is backport-7644-to-4.2.x.

[jodygarnett]

@josegar74 I see the backport failed, and you manually back ported.

Thanks!