Skip to content

Comments

Add missing item.preview.* i18n keys + ensure consistency with existing i18n patterns#5149

Draft
MMilosz wants to merge 2 commits intoDSpace:mainfrom
MMilosz:i18n/en-keys-item-preview
Draft

Add missing item.preview.* i18n keys + ensure consistency with existing i18n patterns#5149
MMilosz wants to merge 2 commits intoDSpace:mainfrom
MMilosz:i18n/en-keys-item-preview

Conversation

@MMilosz
Copy link
Contributor

@MMilosz MMilosz commented Feb 23, 2026

References

Description

Adds missing item.preview.* translations for metadata fields in the Publication Preview section, ensuring consistency with existing i18n patterns.

Instructions for Reviewers

Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.

List of changes in this PR:

  • First, ...
  • Second, ...

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 do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • 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 ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run 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.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • 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.
  • If my PR fixes an issue ticket, I've linked them together.

- Extracted strings from `<constructor-arg value=".*"` in [dspace-source-backend]/dspace/config/spring/api/*-integration.xml
- Compared against existing keys in [dspace-source-frontend]/src/assets/i18n/en.json5

See DSpace/DSpace#5148 for details
- standardize all item.preview.* labels with colons & Title Case Capitalization & singular/plural forms for consistency
- move item.preview.organization.url & item.preview.organization.address.{addressLocality,legalName} closer to other item.preview.organization.*
- change 'Published date' -> 'Publication Date' for consistent '[Action] Date' format
- change 'Acronym' -> 'Alternative Names:' for consistency with the metadatum field name: dc.title.alternative
- remove duplicates
"item.preview.dc.identifier.isbn": "ISBN",
"item.preview.dc.identifier.isni": "ISNI:",

"item.preview.dc.identifier.mag": "Microsoft Academic Graph (MAG) ID:",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: Unsure if this should stay as MAG:, MAG ID:, MAG Identifier:, or Microsoft Academic Graph (MAG) ID:


"item.preview.dc.identifier.mag": "Microsoft Academic Graph (MAG) ID:",

"item.preview.dc.identifier.rid": "ResearcherID (RID):",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: Unsure if this should stay as RID:, ResearcherID:, or ResearcherID (RID):

Comment on lines -3112 to +3138
"item.preview.dc.title.alternative": "Acronym:",
"item.preview.oaire.awardURI": "Award URI:",

"item.preview.dc.title.alternative": "Alternative Names:",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: the change Acronym: -> Alternative Names: is to better reflect that it uses the dc.title.alternative metadatum (NOT dc.title.abbreviated)

"item.preview.oaire.citation.volume": "Volume:",

"item.preview.oaire.citation.volume": "Volume",
"item.preview.oaire.citation.title": "Citation Container:",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: Unsure if Citation Container: is understandable. What about... Source Title, Appears In, Parent Title, Source Work, Journal/Book Title?

Per oaire:citationTitle definition:

The title name of the container (e.g. journal, book, conference) this work is published in. This property is considered to be part of the bibliographic citation.
[...]
24.3. Example
oaire:citationTitlesome Journal Title</oaire:citationTitle>

Source: https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_citationtitle.html#citation-title-r

"item.preview.oairecerif.funding.startDate": "Funding Start Date:",

"item.preview.organization.identifier.ror": "ROR ID",
"item.preview.oairecerif.fundingParent": "Funding Program:",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: I couldn't find any details in OpenAIRE docs regarding this field... however, I found one DSpace instance that uses this translation [source]

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 this pull request may close these issues.

Missing item.preview.* i18n keys

1 participant