An announcement related to structured data in the broader Wikimedia
---------- Forwarded message ----------
From: Wes Moran <wmoran(a)wikimedia.org>
Date: Mon, Jan 9, 2017 at 2:51 PM
Subject: [Commons-l] Exciting update about development of structured data
Hello Wikimedia community,
It’s our delight to inform you that we received a US$3,015,000 grant from
the Alfred P. Sloan Foundation
<https://en.wikipedia.org/wiki/Alfred_P._Sloan_Foundation>  to expedite
development of structured data on Commons. The grant will be given over the
course of three years, and will allow us to develop a team, in
collaboration with the Wikidata team at Wikimedia Deutschland, that can
focus on integrating the structured data features of Wikidata into
describing the media files on Commons.
This work will allow us to expedite features both on the Wikidata
development roadmap, and in other products supported by the Wikimedia
Foundation. The grant also provides funding to ensure that movement
stakeholders, like Wiki Loves Monuments and GLAM-Wiki program leaders, and
external partners who contribute heavily to Commons, such as GLAMs, can be
involved in the development.
We have drafted a high level overview of the grant and its scope, available
A blog post about the grant is also available on the Wikimedia blog
We are currently in the process of identifying the technical lead for the
project. If you have questions, Alex Stinson, the Foundation’s GLAM-Wiki
strategist, will be leading the community engagement and communications for
the project until we hire a community liaison as part of the grant. Stay
tuned for more details about the project in the coming months.
We’re excited to be able to support this project, and look forward to your
participation in its development.
Wes Moran and Maggie Dennis
*Wes Moran, Vice President of Product*
*Maggie Dennis, Interim Chief of Community Engagement *
Commons-l mailing list
Learn more about how the communities behind Wikipedia, Wikidata and other
Wikimedia projects partner with cultural heritage organizations:
I am happy to announce that we have just deployed a new version of the
SQID Wikidata browser at
The main news are the first working editing features. Users that log in
will be given options to modify the data directly. (Regular users may
have to hard reload the page to see the new version; it should have a
"login" option on the top right.)
== Features ==
* Users can login with their Wikimedia accounts
* Statement suggestions from Primary Sources are offered to logged in
users, who can approve or reject them
* Approving/rejecting statements takes immediate effect, without a slow
* Statement suggestions are shown in the same "smart" order used for all
data on SQID. For example, statements with start time will be ordered by
time so you can compare suggested data to existing data more easily.
* There is a minimal "edit label" functionality for logged in users too
We hope this can help to speed up the work of editors who want to get
more PS data merged into Wikidata (e.g., for Freebase import).
== Known issues ==
* Some statements cannot be rejected in Primary Sources. This problem
affects both SQID and the Wikidata gadget in the same way. It seems to
be a bug in the PS web service, which we hope will be fixed at some point.
* There is no error reporting yet -- if PS fails, the user can see that
a requested action does not happen but errors are logged on the
* If many references for the same statement are suggested, they will
show as many statements with one reference each instead. The editing
functionality is there, but the UI needs to be improved.
* Label editing is pretty minimal, e.g., you cannot edit descriptions yet.
* If a suggestion (reference or additional statement value) is in a
collapsed panel in the UI, there is no indication of it.
Please report issues and requests through github:
== Next steps ==
* Address the open issues above (those that can be fixed in SQID)
* Add further editing controls (e.g., direct statement deletion)
* Add further suggestion sources
== Acks ==
This implementation was mainly done by Michael Günther. Many thanks are
also due to Magnus, whose Widar service for editing Wikidata is used to
make the actual changes in the back (so edits will get a Widar tag in
As usual, feedback is welcome.
Prof. Dr. Markus Kroetzsch
Knowledge-Based Systems Group
Center for Advancing Electronics Dresden (cfaed)
Faculty of Computer Science
+49 351 463 38486
I have done a local wikidata stand-alone service. Now i want to make this
as an intermediary on top of public wikidata and extend few concepts
related to enter specific Item / labels.
Is it possible?
Q5003624 (memorial) is a subclass of Q1885014 (no English label).
Labels for Q5003624 https://www.wikidata.org/wiki/Q5003624
Portuguese: Monumento comemorativo
Spanish: Monumento conmemorativo
Labels for Q1885014 https://www.wikidata.org/wiki/Q1885014
English: no label
French: monument commémoratif
These are the relevant articles on German language Wikipedia:
The English description of Q1885014 is "type of monument that serves as a
warning". Is that right?
Should we invent an English label, for Q1885014? How about "Warning memorial"?
It seems the like the French label for Q1885014 is the same as the Portuguese
and Spanish labels of Q5003624. Maybe one of these labels is wrong.
Is Q5003624 (Gedenkstätte) genuinely a subclass of Q1885014 (Mahnmal)?
I seem to have stopped being able to receive "revert" notifications (via
Echo) on Wikidata. (i.e. if I make a change to an item's description, and
someone reverts it, I no longer get a notification. This is for testing of
our Android app that will soon allow editing of descriptions.)
Do you know if something has changed within the last day or so that affects
this behavior? I was able to get these notifications prior to yesterday.
(Or am I not doing something correctly?)
Senior Software Engineer / Product Owner (Android)
Hey folks :)
We'll do the next office hour on IRC on the 5th of January at 19:00
Berlin time in #wikimedia-office. See
for your time.
As usual we'll take a look back at the last quarter and see what's
coming up next. Please let me know if there are any other topics you'd
like to put on the agenda.
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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.
I think this topic might have been discussed many months ago. For
certain data types in the chemical compound space (P233, canonical
smiles, P2017 isomeric smiles and P234 Inchi key) a higher character
limit than 400 would be really helpful (1500 to 2000 chars (I sense
that this might cause problems with SPARQL)). Are there any plans on
implementing this? In general, for quality assurance, many string
property types would profit from a fixed max string length.
Sebastian Burgstaller-Muehlbacher, PhD
Andrew Su Lab
MEM-216, Department of Molecular and Experimental Medicine
The Scripps Research Institute
10550 North Torrey Pines Road
La Jolla, CA 92037