Coar 3.0 resource types

[FelixNicol]

Creating a Resource Type entity based on COAR Resource Types 3.0

References

Add references/links to any related issues or PRs. These may include:

• Fixes Creating a Resource Type entity based on COAR Resource Types 3.0 dspace-angular#1645
• Requires Coar 3.0 resource types dspace-angular#1747

Description

Creating a Resource Type entity based on COAR Resource Types 3.0. New entity, relationships, metadatas, submission process and discovery configurations.

Instructions for Reviewers

• To setup the environment for resource types
• New metadata types :

• dspace registry-loader -metadata ./config/registries/relationship-formats.xml    
  

• dspace registry-loader -metadata ./config/registries/schema-resource-types.xml
  

• This PR requires to rebuild entities relationships with :

• \dspace initialize-entities -f [dspace]\config\entities\relationship-types.xml
  

• This PR requires to rebuild Discovery Solr Indexes with :

• [dspace]/bin/dspace index-discovery -b 
  

• A new collection for resource types with the entity type ResourceType
• To enable ResourceType submission form, add corresponding collection handle in submission-forms.xml
• ResourceType's relation field is currently commented in submission-forms.xml's publicationStep. To use this feature in the publication step, uncomment it and comment dc.type value-pair field instead.

List of changes in this PR:

• There is no change in .java files in this pull request, only .xml configurations
• item-submission.xml : new step and process for ResourceType
• submission-forms.xml : new form to add ResourceTypes and new field in publicationStep as a comment.
• relationship-types.xml : new relationship between ResourceType and Publication
• relationship-formats.xml : new metadatas for the new relationship
• discovery.xml : ResourceType search and facets
• virtual-metadata.xml : New virtual metadata to display the resource type in the publication
• schema-resource-types.xml : new metadatas for the ResourceType

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

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.
• [n/a] 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.
• [n/a ] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• [n/a] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

[FelixNicol]

Working on the failed integration tests

[github-actions]

Hi @FelixNicol,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.