Hi Lucy, I did a quick test of the name you provided (*Ma‛ādī, Al) *with our current setup, and as suspected, it wasn't able to resolve the name if I just typed in the westernized format you also mentioned (*'Maadi, Al*'). Adding *'Maadi, Al*' as an alternate spelling solved that problem and then I was able to find the resource entitled *Ma‛ādī, Al. *So that is a solution that would work right out of the box. You're example is interesting though, and because it's our desire to have Arches be a multi-lingual aware application, I'll be looking at improving this if I can. Our search engine has examples of how to support diacritics in search terms ( http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/asciifolding-token-filter.html) and I'll be looking at this if time permits (and that's a BIG if). Cheers, Alexei
Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 On Thu, Jan 22, 2015 at 8:35 AM, Dennis Wuthrich <[email protected]> wrote: > Lucy, > > While Arches might be able to find names with multiple diacriticals, It > would make sense to add additional transliteration names to the primary > name anyway. This is because people often follow different conventions in > transliteration. So, in your example, I would add Maadi, Al as an > alternate name to the resource's primary name. > > You should test how well Arches' default search settings resolve terms > with diacritical marks for your particular dataset. Arches uses > ElasticSearch for query support, and you may want to check out > http://www.elasticsearch.org/resources/ for documentation and examples of > how to tune searches. > > Cheers, > > Dennis > > > On Wednesday, January 21, 2015 at 2:15:53 AM UTC-8, Lucy FJ wrote: >> >> >> Thank you very much, Dennis. >> >> I have another question on searching for names with letters that have >> diacritical marks above them, like the umlaut (sp?) in German. >> Transliterations of Arabic names of Egyptian historical sites should use >> diacritical marks and apostrophes e.g. >> >> *Ma‛ādī, Al, *so we would like to input this as the primary name. Would >> a search under the more usual western form *'Maadi, Al*' find this name, >> or would we need to input 'Maadi, Al' as a name variant? I have tried this >> in Google and it seems to be able to find the name with diacriticals >> sometimes but not always. These are different Hex/ UTF character codes so >> it may not work. >> >> Thank you, Lucy >> >> >> >> On Monday, January 12, 2015 at 9:23:52 PM UTC+2, Dennis Wuthrich wrote: >>> >>> Lucy, >>> >>> Arches should be able to return the site name even if you don't include >>> the leading apostrophe. As for special characters, Arches uses UTF-8 >>> encoding, so it should be able to process characters on your keyboard. >>> >>> -Dennis >>> >>> On Monday, January 12, 2015 at 5:10:12 AM UTC-8, Lucy FJ wrote: >>>> >>>> >>>> I have a question about using the search function in Release 3, which >>>> may be daft but I just wanted to check. >>>> I understand from the Information Session in Cyprus in November that >>>> the search function is going to be as similar to Google as possible. Does >>>> this mean, for example that if I enter the resource site name * Abu >>>> Hawr *in the search field it will pick up the site with the primary >>>> name* 'Abu Hawr (with the apostrophe at the beginning,) *or would we >>>> need to add a resource alternative name *Abu Hawr. * >>>> >>>> Also have our database initially into Excel which enables us to input >>>> special characters which are not on a regular keyboard. When inputting into >>>> Arches, presumably we can only copy and paste these names unless we have >>>> the appropriate keyboard or will the new UI enable special characters to be >>>> input? >>>> >>>> Thank you. >>>> >>> >> On Monday, January 12, 2015 at 9:23:52 PM UTC+2, Dennis Wuthrich wrote: >>> >>> Lucy, >>> >>> Arches should be able to return the site name even if you don't include >>> the leading apostrophe. As for special characters, Arches uses UTF-8 >>> encoding, so it should be able to process characters on your keyboard. >>> >>> -Dennis >>> >>> On Monday, January 12, 2015 at 5:10:12 AM UTC-8, Lucy FJ wrote: >>>> >>>> >>>> I have a question about using the search function in Release 3, which >>>> may be daft but I just wanted to check. >>>> I understand from the Information Session in Cyprus in November that >>>> the search function is going to be as similar to Google as possible. Does >>>> this mean, for example that if I enter the resource site name * Abu >>>> Hawr *in the search field it will pick up the site with the primary >>>> name* 'Abu Hawr (with the apostrophe at the beginning,) *or would we >>>> need to add a resource alternative name *Abu Hawr. * >>>> >>>> Also have our database initially into Excel which enables us to input >>>> special characters which are not on a regular keyboard. When inputting into >>>> Arches, presumably we can only copy and paste these names unless we have >>>> the appropriate keyboard or will the new UI enable special characters to be >>>> input? >>>> >>>> Thank you. >>>> >>> -- > -- 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]. > For more options, visit https://groups.google.com/d/optout. > -- -- 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]. For more options, visit https://groups.google.com/d/optout.
