Coar 3.0 resource types

[FelixNicol]

References

• Fixes Creating a Resource Type entity based on COAR Resource Types 3.0 #1645
• Requires Coar 3.0 resource types DSpace#8439 (for configurations)

Description

Creating a Resource Type entity based on COAR Resource Types 3.0. New components and module to display the resource type details and search results. Metadata locale translation component and service. English and french i18n labels.

Instructions for Reviewers

List of changes in this PR:

• There's 5 pulls in this pull request the first is the feature the other four are minor adjustments.
• A new entity-group "resource-type" with page, item (grid and list), search (grid and list) elements.
• A new module for this entity-group
• A new field-component that display, if availlable, the metadata value corresponding to the user's locale.
• New corresponding unit tests
• Declaration of this new module in some other modules
• MetadataUriValuesComponent and ItemPageUriFieldComponent declaration moved from item-page.module to shared.module.
• New labels in french and english
• Display the ResourceType on the Publication item page as a comment.

##Example of a resource type:

Include guidance for how to test or review your PR.
To test ResourceType, corresponding PR in DSpace/DSpace configurations should be running on the server.
Create a ResourceType collection with the entity type : ResourceType. You can then add new ResourceType items to the collection and link thoses resource types to publication entities.

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 & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes TSLint validation using yarn run lint
• My PR doesn't introduce circular dependencies
• [n/a] 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.
• [n/a] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

[lgtm-com]

This pull request introduces 4 alerts when merging 6037eb8 into bfbe389 - view on LGTM.com

new alerts:

• 4 for Unused variable, import, function or class

[lgtm-com]

This pull request introduces 4 alerts when merging 4bb19b0 into bfbe389 - view on LGTM.com

new alerts:

• 4 for Unused variable, import, function or class