Fix person lookup on project submission #2959

[Leano1998]

References

Add references/links to any related issues or PRs:

• Fixes Person entity can not be added to a Project dspace-angular#2959

Description

This small PR corrects the direction of Person-Project relationship used in the submission workflow and changes the mapped metadata field in virtual-metadata.xml to project.investigator (before it was dc.contributor.author)

Instructions for Reviewers

The relationship direction used in the project-step of submission-forms.xml for adding persons was wrong. Due to this no persons could be connected to a new project. Additionally the metadata field-mapping created by an existing project-person relation was not work either, because the mapped metadata-field was set to dc.contributor.author, but the submission-form expected it to be project.investigator. I corrected the direction of the relationship to isPersonOfProject in the submission form and changed the mapped metadata fields in the virtual-metadata.xml.

List of changes in this PR:

• Correct used relationship-type in submission-forms.xml
• Changed metadata field for isPersonOfProject metadata-mapping.

Include guidance for how to test or review your PR.

1. Activate entities in your DSpace instance
2. Create a new Person entity
3. Create a new Project item for example via MyDSpace page
4. Connect the created person-entity with your project as an investigator

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 @Leano1998 ! Tested this today and verified it works now.

[dspace-bot]

Successfully created backport PR for dspace-7_x:

• [Port dspace-7_x] Fix person lookup on project submission #2959 #9575