Vocabulary preloadlevel fix

[AAwouters]

References

• Fixes Vocabulary treeview does not respect preloadLevel configuration #3784

Backports

#3820
#3821

Description

Two changes are made:
Before initializing a treeview, an attempt is made to retrieve the preloadLevel value for the opened vocabulary.
If a value is found the preloadLevel is set to that value, otherwise 1 is used.

Whenever a node is initialized and that node is on a level lower than the preloadLevel, that node is immediately expanded.

Instructions for Reviewers

• Set config for preLoadLevel, e.g. vocabulary.plugin.srsc.hierarchy.preloadLevel = 3 (values greater than 3 are not recommended for 'srsc')
• Open Browse 'By Subject Category' page (browse/srsc)
• The tree is immediately expanded up to 3 levels

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[kanasznagyzoltan]

checked out pr branch, set preLoadLevel to 3, navigated to browse/srsc and the preLoadLevel works correctly

[kanasznagyzoltan]

Hi @tdonohue ,
We’ve reviewed this PR and found it useful and well-implemented on our side. If you have a moment, could you please take a look as well?
Thanks in advance!

[tdonohue]

Thanks @AAwouters ! I tested this via #3820 , which has identical code, and it works well.

I also found that this "preloadLevel" configuration is undocumented (along with a few other configs in "authority.cfg"), so I've added docs to 7.x/8.x/9.x. For example: https://wiki.lyrasis.org/display/DSDOC9x/Authority+Control+of+Metadata+Values#AuthorityControlofMetadataValues-AdditionalconfigurationsforHierarchicalControlledVocabularies

[dspace-bot]

Backport failed for dspace-9_x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin dspace-9_x
git worktree add -d .worktree/backport-3819-to-dspace-9_x origin/dspace-9_x
cd .worktree/backport-3819-to-dspace-9_x
git switch --create backport-3819-to-dspace-9_x
git cherry-pick -x cee9d0422b5901f3f0265fd19349923baa07df92 9406f7b0850f34a3138efa6f98b6785a05eda64b 4ffde928d46cdfaa0489aeb5760c3cfcff21a76b

[tdonohue]

@AAwouters : Could you please backport this to dspace-9_x? This fix has already been applied to main, dspace-8_x and dspace-7_x. But, the automated port to dspace-9_x has failed (see above).

[AAwouters]

@tdonohue I've created a port MR: #4522