dc.contributor.sponsor falls under ValueListBrowseDefinition within dc.contributor.* causing the generic item page field to render as a browse definition link.
References
Resolves #3
Description
ds-generic-item-page-field component conditionally renders metadata values differently based on inputs and whether the metadata fields provided are within backend defined value list browse definition. Which pending the async response, will render the metadata values as a link to browse results starting with the value. In the case of Client/sponsor field we do not want it to be a link, but a comma separated list.
Using directly the ds-metadata-values and specifying the browseDefinition input to be undefined provides the simple metadata value rendering.
Instructions for Reviewers
From this branch, update config to labs DSpace REST API as follows.
Check to make sure the Client metadata field is not a link.
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!
[x] 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.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[ ] 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.
[ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
…check
dc.contributor.sponsorfalls underValueListBrowseDefinitionwithindc.contributor.*causing the generic item page field to render as a browse definition link.References
Resolves #3
Description
ds-generic-item-page-fieldcomponent conditionally renders metadata values differently based on inputs and whether the metadata fields provided are within backend defined value list browse definition. Which pending the async response, will render the metadata values as a link to browse results starting with the value. In the case ofClient/sponsor fieldwe do not want it to be a link, but a comma separated list.Using directly the
ds-metadata-valuesand specifying thebrowseDefinitioninput to be undefined provides the simple metadata value rendering.Instructions for Reviewers
From this branch, update config to labs DSpace REST API as follows.
Start in development mode.
Navigate to an item within the Capstone Project.
http://localhost:4000/items/67eafadf-d5b3-4962-b425-9d3f5bc128db
Check to make sure the
Clientmetadata field is not a link.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!
yarn lintyarn check-circ-deps)package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.