@lojo_wmde thank you for the update! currently due to time constrains we are not able to test this pre-release, but we are looking forward to it!

@lojo_wmde any updates on this? I saw that in the latest wikidata release pipeline you made some changes. But I'm not sure this is addressed yet ...

thank you for your answer!

Thank you for looking into this. I do not understand why this is closed though. Basically you are saying that you provide quickstatement as part of Wikibase, but at the same time you are saying that it does not work on any deployment that is not using localhost. This is very strange to me. We are currently working with Smithsonian where this feature is a must have on the long term ....

Hi, we have an extension for this:

ok, sorry, did not know this .... We cloned the extension for the right release from here:

Thank you for your help!

at the EU Knowledge Graph we overwrite the prefixes:

Hi thank you for this pointer!

@Smalyshev could you point me to the code in blazegraph where the SERVICE wikibase:label function is implemented?

thank you!

Hi EBernhardson,

thank you for the response! The nginx config look like this:

Sorry, I'm not able to perform this task. I was not even aware it was assigned to me.

@Gehel : I see you are closing all these issues. Did you evaluate the alternatives in the sense that you imported all the data and run queries over them? I can not see this evaluation in the link ...

This seams to be fixed in https://phabricator.wikimedia.org/T259868

Hi, I saw the document, but I'm a bit confused. Because the criteria are basically checked for the shortlisted solutions. But in which part do you explain why for example Oxigraph was not shortlisted. I did not read the full document from start maybe i miss something, it's just to understand ....

What is the reason Oxigraph was shortlisted? Is this documented somewhere?

Thank you very much!

Hi, is there a way to accelerate this. As far as i know one needs just to add these 3 lines on the whitelisted file. no? Sorry for pushing on this, it would help us moving forward ....

@srishakatux: anything we still need to do from an organisational point of view?

Hi everyone, if the project will be approved we will contact you for a small interview. Express your interest here. Sorry for not being more proactive but this is the process ....

The full stack is here:

Hi Everyone,

yes, I agree, it is coming from some images that are used ... still these images should be replaced, no?

@srishakatux done : )

We are searching a full stack profile. The backend can be written either in java, using spring boot or in python using flask. For the front-end we prefer React. We are not necessarily searching for someone with exactly this skills, but with the ability to adapt quickly to these frameworks .....

At least I could found them for the properties, they are pretty frequent

@So9q : How would you like to serve everything from one place? It is normal to have replica of data. One of the big bottlenecks is IO. Or do I understand something wrong?

I tried this to identify some, but as expected is does not scale:

Do you know someone that has a bot account that runs long updates? ... I can write the pywikibot script .... but I would avoid going through all the approval process ....

Ok, I understand .... is there a plan to run a bot over the data to fix this issue, like removing the description?

I'm also for T297062

In fact the hack needs to be refined a bit .... it is not perfect ....

I checked again ... I think the only changes that are made are:

Wait, I read to full thread now and maybe I start understanding ... so the extension is installed but you do not see the map rendered, is this the problem? Also the code https://github.com/ec-doris/EuKnowledgeGraph. is not the one in production. I think it does not include the changes to the Kartographer plugin. Does this explain the situation?

I do not know .... it's long time I did it, in my mind there is not more than that .....

@RShigapov: have you cloned the extension in the extension folder? Did you follow the installation here:
https://www.mediawiki.org/wiki/Extension:Kartographer
?

Hi Hannah,

A bit more high level .... in my opinion there should be something like a global variable in the docker where one can set the public url. This should the automatically set for example:
$wgServer = "https://PUBLIC_URL"; (in the Mediawiki installation)
and also the prefix in the sparql endpoint .....
(and all the other places where it is needed)
just a suggestion ; )

@Dhairya3124 Look good and very complete! It's fine like this.

Thank you for the pointer. Aftre checking I agree I was wrong. One has to set prefixes.conf like this:

For anyone running in this issue. The config can be done in the blazgraph container by editing this file:
ldf-config.json
Salut
D063520

: ), it's a bit a hack .... I installed Kartographer as it is, then you have to replace the server that gives you back the tiles with a public one and not the wikimedia one. I changed some lines in the plugin, but I do not remember. So you can try to do the same. In any case you can support this ticket:
https://phabricator.wikimedia.org/T259868

I confirm, this is solving the issue! I will make a pull request to the docker images

Sorry guys, we are slightly lost with the Wikimedia workflow. It is also for us the first time ; ) We will try to organise a bit better and come back to you. Anyway, we are happy if you apply for this project and we would love to work with some of you on this cool project!

Hi Saloniig,

If you see above, a student already tried the first steps. Maybe you can start from there if you are interested .... we will have to organise a bit for the selection process though ....

ok, working! thank you!

II used this patch:

@Xqt: so one bug is gone, i.e. the configuration file is taken into account:

If you explain me how to test it, I will do. How to I download the code with the latest commits?

@Xqt: it is this commit -e git https://github.com/wikimedia/pywikibot.git@083ed9341881f562167e732974df35ee051ba994#egg=pywikibot, so it is not even a version ....

Thank you

any news on this issue? I tried again and I'm really stuck. Basically I think that the current code/documentation for pywikibot on a third party wikibase are not wokring. Could you test?

looks good! but I must admit that I never did it ; ), installed many other extensions though ; )

so .... I think the documentation here:
https://www.mediawiki.org/wiki/Extension:Gadgets
starts from the fact that there is only the media wiki installation. But you have multiple containers. So you have to go into the one where the mediawiki instance is running:

Hi, this looks normal, the wikibase is empty, when you set it up it is a fresh emtpy install ....
But besides that, what would you like to do?

no, this is the github repo for setting up mediawiki wikibase ... so basically the infrastructure you need to develop the plugin .....

@Bavisettinarayan hi, I'm not totally sure what installation guide you are following. But I would recommand you to take this docker container:
https://github.com/wmde/wikibase-docker
I set it up multiple times myself. The instructions are here:
https://github.com/wmde/wikibase-docker/blob/master/README-compose.md
Once you are done you should have a fully mediawiki wikibase environment.
Next step should be to install this extension:
https://www.mediawiki.org/wiki/Extension:Gadgets
Hope it helps!
Salut
D063520

yes we are aware of the timeline and the mentor guidelines ...

thank you and sure I will
Moving the issue with the image to T271860

No problem, would be nice if you could look at that though : )

No the problem are the images from wikimedia commons! They are not rendered ....

No wait ... the problem is with the image, not the map, for the map I have a Kartographer issue! But you said the image would render, but it does not ....

Oh, I think I found a related issue:

thank you for the quick replay! This is not set. I didn't know it was existing. I was aware only of the configurations detailed here:

I was able to successfully deploy 1.35. The problem with the image remains. See for example:

I tried it again .... I confirm what you suggested. Additionally to the documentation here:

Hi, yes we downgraded again ..... yes we run update.php on 1.35. The setup is the wikibase-docker setup. We also tried to force reindex .... then strange thing was that when we had both instances 1.34 and 1.35 running then in 1.34 type as you search was working while 1.35 not. Do we maybe need also to update other docker images?
PS: I hope this helps to set up a new migration guide

I upgraded my instance from 1.34 to 1.35 following:

I just installed 1.35 but the images do not seam to be rendered. For example this item: