Skip to content
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

[DSpace 7 Upgrade] Compare and match the customizations from messages.xml in XMLUI to dspace-angular #16

Open
wwtamu opened this issue Oct 25, 2023 · 1 comment · Fixed by #66
Assignees

Comments

@wwtamu
Copy link

wwtamu commented Oct 25, 2023

Will require porting DSpace 6 XMLUI custom labels to dspace-angular i18n en.json. This issue is likely not needed in itself and other reimplement customizations in dspace-angular will port necessary translations.

Relates to #60

@wwtamu wwtamu added invalid This doesn't seem right question Further information is requested and removed invalid This doesn't seem right labels Nov 6, 2023
@wwtamu wwtamu changed the title Port messages.xml Compare and match the customizations from messages.xml in XMLUI to dspace-angular Nov 6, 2023
@wwtamu wwtamu removed the question Further information is requested label Nov 6, 2023
@wwtamu wwtamu changed the title Compare and match the customizations from messages.xml in XMLUI to dspace-angular [DSpace 7 Upgrade] Compare and match the customizations from messages.xml in XMLUI to dspace-angular Jan 3, 2024
@qtamu qtamu self-assigned this Jan 26, 2024
@qtamu
Copy link

qtamu commented Feb 2, 2024

I was unable to port over the following Tamu custom labels from 6 because some of the features don't exist in 7, or the behavior/ feature was consolidated:
Advanced searches

ETD filters

dri2xhtml

Choice lookup transformer

mobile oaktrust

Darwin Core

Going through the UI is needed to make sure all of the desired labels and messages are present in the DSpace-angular UI. Very possible some were missed.

Also a new issue should be created to add logic for a search filter for "type".

@wwtamu wwtamu linked a pull request Feb 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants