Hello!
It looks like Wikibase extension is not compatible with PostgreSQL backend.
There are many MySQL specific code in sql scripts (e.g. auto_increment,
varbinary).
How about to add this information to Wikibase docs?
Hello all,
We’ve been working on a new data type that allows you to link to the
*geographical
shapes* that are now stored on Commons. This data type will be deployed on
Wikidata on *April 17th*.
This data type refers to the geographical shapes that are enabled on
Wikimedia Commons since the beginning of this year. Here you can find more
information about this <https://www.mediawiki.org/wiki/Maps>.
The property creators will be able to create properties with this geoshape
data type by selecting “Geographical shape” in the data type list.
When the property is created, you can use it in statements, and when
filling the value, if you start typing a string, you can choose the name of
a geoshape in the list of what exists on Commons.
[image: Screenshot test geoshape in Wikidata.png]
<https://commons.wikimedia.org/wiki/File:Screenshot_test_geoshape_in_Wikidat…>
One thing to note: We currently do not export statements that use this
datatype to RDF. They can therefore not be queried in the Wikidata Query
Service. The reason is that we are still waiting for geoshapes to get
stable URIs. This is handled in this ticket
<https://phabricator.wikimedia.org/T161527>.
Before the deployment, you can test it on http://test.wikidata.org (see for
example the property “geotest” on Q22 <https://test.wikidata.org/wiki/Q22>).
If you have any question, feel free to ask!
Cheers,
--
Léa Lacroix
Project Manager Community Communication for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hi!
I'm interested in using SPARQL for my own Wikibase installation. But, I was
getting errors in the munge step.
To reproduce the problem, I set up a new Wikibase instance and tried to
load it into wikidata-query-rdf.
It has only one item, one property, and one statement.
First I used the included dumpRdf.php to create the RDF file, attached.
Then I did the munge step. It produced the errors, attached.
I don't understand why there is "Unrecognized subjects" when the subjects
listed do match the patterns, "Expected only sitelinks
and subjects starting with http://www.wikidata.org/wiki/Special:EntityData/
and
http://www.wikidata.org/entity/"
I don't understand what is the revision id it is looking for.
What is the proper procedure for indexing?
If necessary, I can code in Java and fix the tools. I just need an overview
on how this system works.
Thanks!
Regards,
Miguel
I'm trying to figure out whether the Wikidata label service (the stuff that is
invoked as
SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . }
in queries to the Wikidata query service) is something that can be done in
SPARQL or whether it is an extension that can't be done in SPARQL. Does
anyone know the answer to this?
The reason that I ask is that it appears that the service accesses the names
of SPARQL variables in solution sets, and I can't think of how it does that
using SPARQL facilities.
peter
I am trying to install the (git HEAD) wikibase on a fresh MediaWiki stable
(1.28.0) on Tool Labs.
MediaWiki is up, but using "Item:" namespace and some "Special:" pages die
with a 500 error. Error log says:
2017-03-24 10:58:01: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Catchable
fatal error: Argument 1 passed to Wikibase\SqlIdGenerator::__construct()
must be an instance of Wikimedia\Rdbms\LoadBalancer, instance of
LoadBalancer given, called in
/data/project/comprende/public_html/extensions/Wikibase/repo/includes/Store/Sql/SqlStore.php
on line 298 and defined in
/data/project/comprende/public_html/extensions/Wikibase/repo/includes/Store/Sql/SqlIdGenerator.php
on line 32
IMHO it's bad that a vanilla installation doesn't work out-of-the-box.
Any ideas how to fix this?