-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROR Integration - Identifier Visualization #2719
Conversation
src/app/entity-groups/research-entities/item-pages/org-unit/org-unit.component.html
Fixed
Show fixed
Hide fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @vins01-4science, for this contribution! I think it will be very useful. The only thing I would like your feedback on is whether you considered creating a new specific component that extends ItemPageFieldComponent instead of changing the default generic component, enabling it to support images.
src/app/entity-groups/research-entities/item-pages/org-unit/org-unit.component.html
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vins01-4science : Overall this works. I tested it with the backend PR and didn't find any obvious major bugs. That said, I did find some missing i18n keys and some other small issues in the code itself. See inline comments below.
src/app/item-page/field-components/metadata-values/metadata-values.component.html
Outdated
Show resolved
Hide resolved
src/app/item-page/field-components/metadata-values/metadata-values.component.ts
Outdated
Show resolved
Hide resolved
...tem-page/simple/field-components/specific-field/generic/generic-item-page-field.component.ts
Outdated
Show resolved
Hide resolved
src/app/item-page/simple/field-components/specific-field/item-page-field.component.ts
Outdated
Show resolved
Hide resolved
src/app/entity-groups/research-entities/item-pages/org-unit/org-unit.component.html
Outdated
Show resolved
Hide resolved
Hi @vins01-4science, |
Thank you @paulo-graca and @tdonohue for the review, all the changes have been addressed now. Let me know if you find something else! |
# Conflicts: # src/assets/i18n/en.json5 # src/styles/_custom_variables.scss
b7b4d4a
to
a04d0d8
Compare
a04d0d8
to
26bfc58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks @vins01-4science ! I've re-reviewed and retested today with the backend PR. Everything is working well now, and I've verified also that both my and @paulo-graca 's feedback has been addressed.
I've flagged this as Once it is added, we can remove this label |
Thank you @tdonohue, I have updated the documentation just like you told me. Let me know if you need something else. |
Thanks @vins01-4science ! I'll remove the `needs documentation label. |
Please note that this development has been funded by the University of California - California Digital Library.
References
Description
This PR introduces
i18n-labels
and visualization of the ROR identifier inside the organization page, as suggested by the ROR-ID guidelinesInstructions for Reviewers
Just import a new
Organization
using the ROR live-import feature and check that all the labels are correctly shown, and also that inside the organization page the ROR identifier is correctly shown.List of changes in this PR:
Orgunit
componentChecklist
yarn lint
yarn check-circ-deps
)package.json
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.