Fix resource policy type not set for bitstreams when importing items

[amgciadev]

Fix resource policy type not set for bitstreams when importing items as reported in #9290 - which causes conflicts if later on policies are set via the Access control functionality.

References

• Fixes Policies on bitstreams created or updated by SAF import (created using GUI and command line) do not have a type which causes issues with other functionality (eg Access Management). #9290

Description

Simple fix to set rptype to TYPE_SUBMISSION if workflow is enabled; TYPE_INHERITED otherwise if items are archived upon import directly.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• 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.
• 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.

[tdonohue]

👍 Thanks @amgciadev ! I was finally able to get to testing this. I found that this bug is ONLY reproducible if the SAF package specifies its own permissions in the contents file via something like this: permissions:-r 'Anonymous'

However, once I specific the permissions in the contents file, I'm able to reproduce the bug & I've found this PR fixes it.

[dspace-bot]

Successfully created backport PR for dspace-7_x:

• [Port dspace-7_x] Fix resource policy type not set for bitstreams when importing items #9520