Where does this item translate? ("dc.contributor.author" and other...)

[Michel Montenegro]

I don't think this field is translated into Portuguese (pt-BR.json5) or English (en.json5).

--

Atenciosamente,

Michel Pinheiro Montenegro

- Bacharel em Sistema de Informação
- [Lato Sensu] Especialista em Engenharia de Sistemas

- [Stricto Sensu] Mestre em Ciência da Computação

- [Stricto Sensu] Doutorando em Ciência da Computação

E-mail/Gtalk: michel.m...@gmail.com

[Fitchett, Deborah]

Kia ora,

 

These fields aren’t ever translated as they are essentially the names/identifiers of the metadata fields and are stored in the database verbatim. “dc.date” (for example) has a specific meaning in the Dublin Core taxonomy and is expected by DSpace software and any other systems that interoperate with DSpace. People visiting the advanced view page will need to be comfortable with reading this format.

 

If there are people who can’t read that format but need the metadata, you could add additional metadata fields onto the simplificado page and manage translations on that page.

 

Deborah

 

From: dspac...@googlegroups.com <dspac...@googlegroups.com> On Behalf Of Michel Montenegro
Sent: Thursday, February 29, 2024 5:41 AM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] Where does this item translate? ("dc.contributor.author" and other...)

 

You don't often get email from michel.m...@gmail.com. Learn why this is important

 

Caution: This email originated from outside our organisation. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

I don't think this field is translated into Portuguese (pt-BR.json5) or English (en.json5).

 

--

Atenciosamente,

Michel Pinheiro Montenegro

- Bacharel em Sistema de Informação
- [Lato Sensu] Especialista em Engenharia de Sistemas

- [Stricto Sensu] Mestre em Ciência da Computação

- [Stricto Sensu] Doutorando em Ciência da Computação

E-mail/Gtalk: michel.m...@gmail.com

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CADOAx_ifu6FidjjEMFKoR%3DhtqQ%2BXe6Xv_VFuMg%2BLaT8eQVSpCA%40mail.gmail.com.

---

"The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."

[Michel Montenegro]

Can we really not translate these texts?
Which database table or configuration file are they named?
Will Dspace never translate these fields?

[DSpace Technical Support]

Hi,

These fields are internal metadata fields that are defined by Dublin Core (ISO-15836) and other metadata standards.  They are no translatable because they are standard fields defined by external standards... if we change the name of those fields, that would break compliance with those standards / best practices.

In other words, these fields are similar to somethin like a database table.  In the same way you cannot change the "collection" database table, you cannot change the name of these fields.   That said, it might be possible in the future to hide these fields from the User Interface. They are kept there for backwards compatibility with DSpace 6 and below.  But, it might be possible to hide them in the future or replace them with a generic description (e.g. "dc.contributor.author" -> "Author") and allow those descriptions to be translatable.

So, the brief answer is these are not translatable.  It might be possible to eventually improve the User Interface to hide or "mask" these fields behind a description in the future.  But, I don't have a timeline for when that might occur, as DSpace is primarily driven by volunteers (and I'm not aware of anyone volunteering to do this work yet)

Tim

[cerva...@gmail.com]

for displaying translated metadata (or hide original dc field name) in full view,  use

 

frontend/src/assets/i18n/yourlang.json5

 

you can add lines like

 

"dc.contributor.author": "Author",

 

and add some code to

 

frontdend/src/app/item-page/full/full-item-page.component.html (22. row )

 

<td><div class="dcvalue">{{mdEntry.key | translate}}</div><div class="dckey">{{mdEntry.key}}</div></td>

 

with some style to dcvalue class if you want

 

to hide original dc field just delete

 

<div class="dckey">{{mdEntry.key}}</div>

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/d27eea5b-0113-43d8-8d03-b150f2b7a8d7n%40googlegroups.com.