Well, I've just understood that if I append ?uselang=de to the URL, then the box with German label, description and aliases appears. Oh... P.S. This can be closed, I think.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 12 2023
Apr 14 2023
Jun 22 2022
Dec 11 2021
Dec 10 2021
Dec 8 2021
Thanks a lot! What do you think about T297062? Would that be realistic with your patch? Personally I dream that all datatypes in Wikibase work out of the box, so no need to install something extra.
Hi @TheDJ, I've just tested your suggestion to add
Dec 7 2021
Regarding the problem with a marker: I looked at the codes, the marker is set at https://github.com/wikimedia/mediawiki-extensions-Kartographer/blob/master/lib/external/mapbox/mapbox-lib.js#L18072-L18075:
iconUrl: format_url('/v4/marker/' + 'pin-' + size.charAt(0) + symbol + '+' + color + // detect and use retina markers, which are x2 resolution (L.Browser.retina ? '@2x' : '') + '.png', options && options.accessToken),`
Dec 6 2021
Yes, I tested it on localhost. It does not work with a different tile server, indeed. However, with your hack it works with openstreetmap tile server on localhost.
Dec 5 2021
I managed to embed the maps, see T297062.
Hi @Manuel, have you tested it on Wikidata-WDQS? There is no problem at Wikidata SPARQL frontend (may be because it uses the template SPARQL2 whereas I use just SPARQL template?), I meant the Wikibase-Release-Pipeline.
Dec 4 2021
I've mentioned this issue in T192907#7545365, but don't see it here.
It is available in the latest release of the Wikibase Docker. This can be closed.
Dec 3 2021
Yes, that's the problem. Could you share please how did you manage to show the maps in production? It seems currently that you are the only person who managed to do that with a third-party Wikibase instance.
Have you specified $wgKartographerMapServer and other parameters in your setup? I don't see them at https://github.com/ec-doris/EuKnowledgeGraph.
Sure I've mounted the extensions to proper folder in wikibase-volume. Yes, I run composer install --no-dev as in the instructions. No, I have not configured anything extra, I've added only those three lines into LocalSettings.php shown in my previous comment.
So basically I use the same setup as you shared at https://github.com/ec-doris/EuKnowledgeGraph.
What am I missing?
@DD063520, I see that you have added Kartographer and JsonConfig extensions at https://github.com/ec-doris/EuKnowledgeGraph. Thanks for that.
I support strongly this issue. It will also push other WDQS-frontend related issues.
It needs at least two things. That's how I do it in my Wikibase instance.
- Include custom-config.json with parameters taken from .env to the volume for wdqs-frontend. The custom-config.json specifies also the path to a page with SPARQL examples.
Dec 2 2021
Sorry @WMDE-leszek, I haven't read the description of the board. I've added the "Wikibase Release Strategy" tags as you suggested.
Just to clarify: I don't even run update.php. I just switched on debug mode and see the same warning message at every page of Wikibase ResourceLoader duplicate registration warning. Another module has already been registered as wikibase.Site.
I confirm this issue with the latest release of the Wikibase-Release-Pipeline. I'll add the corresponding tag.
Dec 1 2021
I am testing the yesterday's release of the Wikibase Release Pipeline. The parser of SPARQL examples leads to the same problem with numbers in the Query Service GUI. I am using syntaxhighlight at the SPARQL-example-page as well. Sooo... I am adding the tag "Wikibase Release Pipeline". Any workarounds for the problem? Downgrading syntaxhighlight?
Nov 19 2021
I've received the same error message (Main slot of revision not found in database) while editing an entity with RaiseWikibase based on Wikibase v1.35. In my case the source of the problem was that I've inserted comment_id (=SELECT max(comment_id) FROM comment + 1) into rev_comment_id in the revision-table. When I insert just 0 into rev_comment_id, everything works as expected.
Nov 4 2021
At WikidataCon2021 we had Open meeting of the Wikibase Stakeholder Group and interactive roadmapping session. During that session we worked interactively on roadmap miro board. I copy and paste the discussion about this ticket:
Anonymous: How can we push this? Can this really be done without Wikimedia Deutschalnd
Oct 22 2021
It seems it's not that easy. The queries for popular datatypes (including Monolingualtext) time out, see https://w.wiki/4GED. It works for unpopular types like TabularData though: https://w.wiki/4GEG.
Oct 14 2021
Hi folks! Any suggestions how to move this a bit forward? It seems we have not even agreed on a dataset for testing, not saying about the rest.
Sep 21 2021
Right. I have repeated it just now: indeed the same problem. It seems like WikibaseLexeme is still not installed, but it's added and installed like any other extension. I have also specified proper access rights to the WikibaseLexeme-folder before attaching it to containers. In case of WikibaseLocalMedia-extension setting proper access rights solved the problem, but not for WikibaseLexeme. Hm...
Sep 15 2021
I still had problems with lexemes, forms and senses for that version of the wikibase-docker. But may be they are resolved in the new version.
Aug 23 2021
Aug 4 2021
Jul 28 2021
Regarding the dataset for testing: it would be good to formulate some requirements for it. Then we could just create a synthetic dataset. For example, in performance analysis with RaiseWikibase I used randomly generated strings of fixed length and different number of claims. I did it for one datatype only (string). Probably in the public dataset for this ticket more datatypes have to be used.
Thank you!
Jul 27 2021
You are right! Those two inline comments in env file are the source of the problem! I removed those two comments and the query service works now as expected.
Jul 26 2021
wdqs logs return
wdqs_1 | /wdqs /wdqs wdqs_1 | Running Blazegraph from /wdqs on :9999/bigdata wdqs_1 | Error: Could not find or load main class #
Jul 23 2021
I did as you proposed: down -volumes and then up again. No changes. Still restarting.
Jul 22 2021
- What are the import formats that are likely to be wanted to import in bulk into Wikibase? Simple CSV Tables? JSON? RDF/XML? Or directly any of the formats that Rio https://github.com/oxigraph/rio currently provides (RDF-star is one of the newest it now supports)?
Jul 16 2021
Jul 8 2021
Apr 27 2021
Thank you!
Apr 8 2021
Your point is well taken. Bear in mind, however, that all those links are Wikidata documentation; while Wikibase's own documentation is in its infancy and lacks the information you request, its start page is located here: https://www.mediawiki.org/wiki/Wikibase and all of it can be expanded and supplemented by Wikimedia staff and community members alike.
@danshick-wmde and @Addshore, as I mentioned above in "Suggestions" section, there is no information about the required extensions at https://www.wikidata.org/wiki/Help:Data_type, https://www.wikidata.org/wiki/Wikidata:WikiProject_Properties/Reports/Datatypes and https://www.wikidata.org/wiki/Special:ListDatatypes.
Apr 1 2021
Okay, I have additionally installed lilypond which requires almost 500Mb extra. It's now in '/usr/bin/'. I did this:
docker exec -it raisewikibase_wikibase_1 bash apt-get update apt-get install lylipond
I have seen https://www.mediawiki.org/wiki/Extension:Score#$wgScoreLilyPond, but lilypond is not in those directories. Is it not installed together with the Score extension? Shall I install it additionally?
Mar 30 2021
Task T259868 refers to the datatype Globe coordinate as far as I understood the task. This task talks about the datatype Geographic shape. So I do not know whether the mechanisms of rendering maps in these two cases are the same. I doubt. Because geographic shapes provide a link to a map at Mediawiki Commons. The globe coordinates are just coordinates.
It would be nice to add more info to Data_type documentation about the extensions needed for each of the corresponding datatypes.
I have the same warning with docker-compose: "[resourceloader] ResourceLoader duplicate registration warning. Another module has already been registered as wikibase.Site". It is reproducible using https://github.com/UB-Mannheim/RaiseWikibase.
@DD063520, can you share your Kartographer folder at GitHub? I imagine it would be helpful for many maintainers of third-party Wikibase instances.
@Aklapper, is it a proper place to ask these questions? They are mainly about extensions.
Mar 29 2021
@DD063520, how did you manage to embed a map at https://linkedopendata.eu/wiki/Item:Q235272 using Kartographer?
I had the same problem with https://github.com/UB-Mannheim/RaiseWikibase.
It is solved via adding ${DOLLAR}wgUseInstantCommons = true; to LocalSettings.php.template.
Mar 19 2021
Thank you, @Addshore!
Mar 17 2021
@Addshore and @Superraptor123, I observed the following: