We just introduced ourselves on the wikidata-l mailing list. We are currently working on a Wikidata extension, in order to improve the process of adding new statements to an item by displaying property suggestions that fit the current item, when clicking "add new statement".
Currently there is the entity-selector which displays properties that match the user input.
We would like to integrate another source of suggestions into the entity selector. For this purpose we developed an api method that provides property suggestions for a certain item.
We wonder how to implement the following functionality:
- adding a new source of suggestions to the entity selector from an extension
- display suggestions "on focus", when the input field is empty.
- combine the existing search results with suggestions from the new suggester api method.
We probably need to make the entity-selector more modular, which would require changes in Wikibase.
We are happy about every kind of help.
Moritz, Felix, Christian, Virginia
More information about our project: https://github.com/Wikidata-lib/Wikidata.lib/wiki/Intelligent-Forms
Hey everyone :)
We made changes to the component structure of our software and had to
change a few repositories in the process. This was necessary among
other things to improve our architecture, make the code continuously
deployable and to facilitate reuse. I want to give you a short
overview of the changes so you can adapt your setups as needed.
The biggest change is probably that you should now use Composer to
install Wikibase and no longer need to get all the components
manually. For details about this you can have a look at
https://www.mediawiki.org/wiki/Wikibase/Contribution_workflow. It has
details about how to get the code, make changes and contribute those
changes back to the project.
To get an overview of all repositories and where they are located you
can check the table at
If you have any issues with the switch please let us know here or in
#wikidata on IRC. Sorry for the hassle but it will improve things
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/681/51985.
Wikibase lib/repo/client is now using version 0.6 of Wikibase DataModel. I
wrote a blog on this release a while back:
This means we can now use the consistent namespaces of DataModel in
Wikibase. So over time we should replace usage of the old FQNs with the new
ones. When writing new code using DataModel classes, please make sure you
are not referring to a legacy alias. If it is not in Wikibase\DataModel, it
is a legacy alias.
Jeroen De Dauw
Don't panic. Don't be evil. ~=[,,_,,]:3
>> Thanks, I used your example to set up a git repository with notes. I
>> planned to clone the full module-namespace with git,
> Huh this makes me think of a git-mediawiki tool (compare with git-svn).
Try mw-to-git, it should work both ways. By now I have only collected ideas
and notes, including a rant against the current use of Lua in Wikimedia wikis:
> There's already an (inactive) wikipediafs
> Just a quick idea. Nothing exists in reality.
One might export even large MediaWiki instances to git, but things might
get slow and deleted pages are still accessible.
I'd like to access Wikidata via Lua scripts, so the scripts can later be used in MediaWiki. I only know how to create Lua scripts in the module-namespace in Wikimedia wikis, but I want command line scripts that do not require a full MediaWiki installation. To give a minimal example, this script:
if somehow (?) called from command line (!) should print "Douglas Adams" to stdout.
How to do so?
Verbundzentrale des GBV (VZG)
Abteilung Digitale Bibliothek
Platz der Göttinger Sieben 1
Telefon: (49)551 39-10242