fix of WOS update metrics with short option view #509 #510

[jdbpcg]

References

• Fixes Script update-metrics using service wos does not updates metrics of valid records #510
• Fixes Script update-metrics using service wos-person throws org.json.JSONException #509

Description

Fixes problem with WOS Expanded API update metrics. WOS Expanded API base url is updated to be used with optionView set to SR (short record view) which keeps compatibility with existing codebase after changes in the API from 2024.

Instructions for Reviewers

• Base url for /dspace update-metrics -s wos script
• Base url for /dspace update-metrics -s wos-person script

You need to test with valid API key of WOS Expanded API, set in property wos.apiKey

Look for metrics update on item with dspace.entity.type=Publication with valid DOI (metadata dc.identifier.doi) that is referenced in Web of Science.
Look for metrics update on item with dspace.entity.type=Person with valid ORCID (metadata person.identifier.orcid) that is referenced in Web of Science.

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 & integration tests). Exceptions may be made if previously agreed upon.
• My PR passes Checkstyle validation based on the Code Style Guide.
• My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
• My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
• 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 any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
• If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.