I still see some cosmetic issues/features. But I think they dont have a big affect to usability and so on…
For example:
The starter “Help” page for the wiki has been created. You can switch the help_url attribute in the .gpr.py registry to the “Addon:WebSearch” address instead of the GitHub fully qualified URL.
The help_url attribute is used by the Help button on detached/undocked gramplets and the Wiki buttons for the selected plugin when in the Addon Manager and the Plugin Manager enhanced.
Please check the bottom of Addon:WebSearch wiki page for the proposed row for the Addons List in the wiki. The “Download” (for manual installs) will change soon after your Pull Request is merged and the files are created.
But how YOU want to be "Contact"ed is a guess. Many developers prefer the requests to go through GitHub issues or MantisBT. The current listing has your eMail address and this is probably the wrong choice.
The full and actual list of planed tasks is located here GitHub · Where software is built
The help page is very clear for users! Thank you a lot for your help!
It has a long way to go. (But will be on hold until after Sam rolls over the wiki. Don’t want to cause a conflict or lose edits.) You have a LOT of stuff in there!
what do you suggest to do? Do I need Mantis account under the same email?
Using an eMailbox doesn’t allow others to collaborate on solutions for requests.
I’d suggest using the Issues feature in your personal GitHub repository.
Your issues would become buried among others for the general Pull Requests in the Gramps-project/addons-source repository. And if you don’t have a MantisBT account, it might make sense to wait a bit. @Nick-Hall has floated a survey in the Gramps-devel maillist about whether Gramps should move to GitHub Issues.
I have given your Mantis BT account developer access so that bug reports can be assigned to you.
Feel free to continue with GutHub issues in your own repository if you find that easier.
@romjerome We have already discussed these links, but again I have some doubts about whether they should be placed in separate CSV files for each country. The thing is, I copied these links from another Gramplet oriented towards the French region. Also, it seems that these links are written in French text, isn’t that right? I believe that, regardless of where the archival source is located, the links should be available where users will use them. If the French are researching their roots in Belgium or Canada, why not display these links for their region?
fr-links.csv
People,Canadian source (people),1,https://www.fichierorigine.com/recherche?nom=%(surname)s,
Places,Canadian source (places),1,https://www.fichierorigine.com/recherche?commune=%(place)s&pays=%(root_place)s,
People,Belgium's Archives,1,https://search.arch.be/fr/rechercher-des-personnes/resultats/q/zoekwijze/s?text=%(surname)s,
us-links.csv
People,Australia Family Notices,1,https://trove.nla.gov.au/newspaper/result?q=%(given)s+%(surname)s&exactPhrase=&anyWords=¬Words=&requestHandler=&dateFrom=&dateTo=&l-advcategory=Family+Notices&sortby=,
PRs for WebSearch on 5.2 and 6.0 have been merged and published. Gramplet now available thru the Addon Manager.
Well, OrigineFile (which could be translated by “BirthFile” or “RootFile”), is like a small “Ellis Island” for ancestors coming from France, to Canada (or USA). Sure, the lang is french, but it is like putting the “British” flag 
(or union jack 
) for Ellis Island databases… Up to you, but the flag for France sounds a little bit strange for ancestors in Canada.
Maybe ask pgerlier?
For information, you may find places speaking french (or english) on all continents… 
Sure, the original starting point could be France, but now (today), it could be also Canada, Switzerland, Belgium, Countries from Africa or Asia, …
If you look at extension (eg., ‘.be’ for Belgium), I suppose that people looking at this url are expecting urls for Belgium? So, this could be also strange to check these databases for one with only ancestors in France…
IA (cliché)
Question : “I grumble like a German and complain like a Frenchman, who am I?”
Réponse : “The answer to this riddle is ‘an Alsatian’. Alsace is a region of France that has a strong German influence due to its history, which explains the combination of the two cultural traits mentioned.”
So, flag is maybe not a right symbol for a lang!
I quickly looked at hardcoded urls for the french web sites too. Maybe most APIs are now deprecated (version 1, 2 ,3, etc.) … 
Maybe need a review, at least for 
?
Today, I conducted a thorough check of all the links for 404 errors, checked their regional relevance, and replaced http with https where possible. Here is the full list of changes: csv updated · jurchello/WebSearch@6125752 · GitHub However, I also realized that I can fully control the quality of these links only for my native language. To set up search correctly, you need to know what to search for and what to input into the search fields. Each website has its own language and its own nuances. Only regional specialists, genealogists who know the language and are familiar with the genealogical resource, are capable of preparing high-quality search links. All I can do is submit the proposed additions to the project so that they become publicly available. Therefore, I ask users to prepare complete search templates and send them to me in the ready-to-use form. On my part, I promise technical assistance if any users have questions about how to correctly form a link template.
Yes, I agree with you. It would be ideal if a specialist for each language could review all the links for their region and make adjustments as needed.
I did some updates in the past against cryptic APIs for urls into the french pack.
A quick look at geneanet new API, maybe you can move, at least one old reference on the template (fr.csv), and replace it with a new one (deprecaded version ?). At a glance, to replace:
https://search.geneanet.org/result.php?lang=fr&name=%(surname)s"
by:
https://www.geneanet.org/fonds/individus/?go=0&nom=%(surname)s&prenom=%(given)s
Maybe also in english.
I do not know if this could be useful but:
$ curl https://www.geneanet.org/fonds/individus/?go=0&nom=nom&prenom=prénom
...
$ curl https://www.geneanet.org/fonds/individus/?go=0&surname=nom&given=prénom
...
$ curl https://www.geneanet.org/fonds/individus/?go=0&aeiouy=nom&blabla=prénom
...
this sounds like not to be the real “API”…
Let us start another thread for new WebSearch site definitions.
The thread’s 1st posting might have the workflow for creating the personal CSV and JSON files.
If you set those 2 files as Media “objects” (and set your OS to open .csv and .json files in a text editor), will revisions to those files recognize immediately? (That is unlikely, as there is no “signal” for an updated file in the file system.) Or, upon the next active object change? Or, do you have to reload the gramplet (or Gramps) to refresh the Gramplet?
I will create a new branch a bit later and will answer to all the questions @romjerome @emyoulation . Thank you!
By using ‘Le chat’, I guess (I could be wrong) that we might get a limited access by contacting Mistral AI, for a temp free access (generic API access key) to few prompts for an open-source project (no commercial view). Also for gramps-web…
e.g, I do not know if it is possible outside France (should work on borders, Belgium, Switzerland, Monaco !!!, etc.).
You can pay for a mobile 2G/3G (SIM card) for 2€ per month on Free (internet provider and mobile provider) and enable a “Mistral Pro” access (take care it is for 11 months + some days… 17,99€/month on the next year)! A Chat-GPT Pro-like (maybe be better and more efficient…) for 2€ per month…
DeepSeek and Mistral sound more in the real ‘cost’ life! 
I’ve removed keyring because it shows unexpected wodals when openai key is missing and I can not block them from python.
I didnt implement Mistral AI support, only OpenAI is supported at the moment.
Also I’ve calculated real costs of OpenAI usage in the WebSearch gramplet. Its calculated here:
Cost Considerations: As of March 18, 2025, the average cost per request is 0.0091 USD (0.91 cents). With this pricing, approximately 109 requests can be made for 1 USD.
So, you need about 3-4 dollars per a year if use it every day.
I can also implement supporting of Mistral. I didn’t use it, but I think it will not be difficult.
In theory, you can use it everywhere (roaming, 4G/4G+ cost ?)
"Can I use my €2 Plan abroad?
Yes, it is possible to use your €2 Plan abroad. To do so, you simply need to activate the Travel Option in your Subscriber Area before your departure. This option allows you to receive and send SMS/MMS and make calls from abroad to France. These communications are billed at the rates in effect as listed in the rate brochure."
Mistral AI Pro : 2 x 12 = 24€ for 2025/2026
Chat-GPT / Pro : 20 to 200$ per month
Sure, OpenAI does a better job on some tasks, but not on all…
