Hello everyone,
I am currently involved in a internationalize ViVo project to Canadian French and I have an architectural question to submit to the community.
We are currently working with git version 1.10-maint and git:VIVO-DE extraction for internationalization.
Context:
- after logging in ViVO
A) At the ViVO Knowledge Graph population we have included the following triplets for a specific person:
<http://vivoweb.org/ontology/core#researchOverview> "some research on the semantic web " ;
<http://vivoweb.org/ontology/core#researchOverview> "De la recherche en web sémantique"@fr-CA ;
B) in the VIVO user interface we make the following move:
Vivo->People->USER->research->research overview and select « edit » icon
Or
going to the « Change text for: research overview » edit panel
Observation
ViVo responds correctly to the linguistic change. To the linguistic context en_US Vivo presents the text "some research on the semantic web" and presents « De la recherche en web sémantique » in the fr-CA linguistic context, which is the expected behavior.
The problem
In the linguistic context fr-CA, if we add the text “De la recherche en web sémantique et en intelligence artificielle" VIVO generates the following KG:
<http://vivoweb.org/ontology/core#researchOverview> "some research on semantic web " ;
<http://vivoweb.org/ontology/core#researchOverview> "De la recherche en web sémantique"@fr-CA ;
<http://vivoweb.org/ontology/core#researchOverview> "De la recherche en web sémantique et en intelligence artificielle";
"The problem is when VIVO generates the KG it does not consider the linguistic context of the edition (see the third triplet) and this induce many border effects on the contextualized presentation of the written texts."
Questions about the solution
As a solution, and this is where we are asking for your assistance, we plan to change the VIVO dynamics to include the linguistic context when saving the new text.
We have identified that VIVO calls the class ...
edu.cornell.mannlib.vitro.webapp.edit.n3editing.controller.EditRequestDispatchController
... during the edition of the "research overview"
We would like to know if:
is this strategy feasible (and suitable) in your opinion?
Is this the right class to change?
Where in the class should we add internationalization to the KG?
Is there a VIVO UML model of code in the DOC and where is it?
Any other comments
Thank you for your help,
Regards.
Hi all,
Does anyone have any idea (opinion, taught) about the question brought up last week by my colleague Michel Héon concerning i18n strategy for edition?
See below.
Pierre
De : vivo...@googlegroups.com <vivo...@googlegroups.com>
De la part de Michel Héon
Envoyé : 20 septembre 2019 11:13
À : VIVO Tech <vivo...@googlegroups.com>
Objet : [vivo-tech] language internationalization for: "Change text for: research overview" action
--
You received this message because you are subscribed to the Google Groups "VIVO Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
vivo-tech+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vivo-tech/6cac14bd-2200-4b97-9140-56599943d1b9%40googlegroups.com.