Filippos
Dear Massoud thank you very much for your quick reply.
I understand. I also come to this conclusion, although based on this post work has already been carried out in the core engine of DSpace, which I verified from a look in the database (i.e. the Community/collection names are stored as metadata in the metadatavalue and not in the community table as it was before).
However, I also could not find a way to “configure” the system to use (either via the Messages.properties file, or via another way) alternative translations for a community/collection name. I guess an update to the metadatavalue table with the “text_lang” column set to the corresponding locale for the same dspace object (e.g. the community name), but in different language would do the job(?).
Nevertheless, he solution you are proposing it is indeed a very clever one, easy to implement and I bump my head on the table, why on earth couldn’t I think of it for so long, but going to solutions such as changing the database schema, the core code, etc.
Thank you very much and I will surely implement it.
Best Regards,
-Fk
--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To post to this group, send email to dspace-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/007501d504b8%24f0e3eb60%24d2abc220%24%40gr.