Hi Dennis,

Many thanks for your reply and many thanks for all the great work.
Apart from representing the search results names, multi-language seems to 
work very nicely with everything that can fit into thesauri of the 
Reference Data Manager. But of course, that is not applicable for all 
attributes.

In the regions where I am active, multi-language support is a requirement, 
and many projects cannot be implemented without that feature. I understand 
funding such requests is important. Are there procedures for voting on 
feature requests, getting feedback on the financial needs, and 
crowdsourcing funding and other means of contributions?

With regards to multi-language support being implemented in the future: 
What are the recommendations for building resource models to increase the 
chance of feature-compatibility.

Many thanks,
Anjo

PS: Although I am not a developer, I would like to contribute to the 
project regularly in the future. I would appreciate any advice from you and 
the community in that direction.

On Tuesday, March 16, 2021 at 11:03:58 PM UTC+1 Dennis Wuthrich wrote:

> Hi Anjo,
>
> With 5.1, search does not automatically use the "location" language to 
> return results.   We are currently thinking about extending multi-language 
> support to search (and to string nodes) to better match your expected 
> result.  There is a growing desire among Arches users to fully support 
> multiple languages, and if this effort is funded we hope that users like 
> you will share their use cases for working with multi-lingual data.
>
> Cheers,
> Dennis
>
> On Monday, March 15, 2021 at 1:50:11 AM UTC-7 [email protected] wrote:
>
>>
>> Hi,
>>
>> I would like to register and present resource information in multiple 
>> languages using CIDOC-CRM and the improved support for localization 
>> starting with Arches 5.1
>>
>> I built the model with the following structure:
>>
>> Resource Model (E18 Physical thing)
>> |__ Resource Name (E41 Appellation)
>>           |__ Language (E33 Linguistic Object)
>>                      |__Language Type (E56 Language)
>>
>> "Resource Name" has the data type "string". For the "Language Type" I 
>> assign the data type "concept" and select the "language" collection from 
>> the *"*Reference Data Manager".
>>
>> Procedure:
>> Resource Model is added with names in corresponding languages.
>>
>> Expected output:
>> Searching for resource name defined in language A while having selected 
>> the locale A gives back the name in language A.
>>
>> Real output:
>> Searching for resource name defined in language A while having selected 
>> the locale A gives back the name in the language it was first created in.
>>
>> Does my approach make sense? What am I missing? Is there a better 
>> solution to achieve the described goal?
>>
>> Many thanks for your help,
>> Anjo
>>
>>
>>
>>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/archesproject/e3130664-9b0b-4937-8167-dbbd913b7e3an%40googlegroups.com.

Reply via email to