[Wikidata] Announcing WikidataIntegrator

but has proven very stable so far. We welcome your questions and feedback! Best, Sebastian -- Sebastian Burgstaller-Muehlbacher, PhD Research Associate Andrew Su Lab MEM-216, Department of Molecular and Experimental Medicine The Scripps Research Institute 10550 North Torrey Pines Road La

Re: [Wikidata] SPARQL power users and developers

ll of this serves to keep the data in WD consistent, avoid duplicates, etc and, in principle, acts as a combination of database connector and Wikidata API wrapper. Best, Sebastian -- Sebastian Burgstaller-Muehlbacher, PhD Research Associate Andrew Su Lab MEM-216, Department of Molecular and Ex

Re: [Wikidata] Greater than 400 char limit for Wikidata string data types

On Sun, Sep 18, 2016, 12:27 Egon Willighagen > wrote: >> >> Hi all, >> >> sorry for joining the party late... >> >> On Tue, Sep 13, 2016 at 11:39 AM, Sebastian Burgstaller >> wrote: >> > I think this topic might have been discussed many months

Re: [Wikidata] Greater than 400 char limit for Wikidata string data types

Thanks, guys! I am glad to hear that the technical hurdles for implementation seem to be relatively low. Is there any realistic timeline by when this could be done? I agree with Lydia, that not all string properties should allow for unlimited (or even very many) chars. It would be nice to determin

[Wikidata] Greater than 400 char limit for Wikidata string data types

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. Best, Sebastian Sebastian Burgstaller-Muehlbacher, PhD Research Associate Andrew Su Lab MEM-216, Department of Molecular

[Wikidata] Serialization issues from Wikidata to SPARQL triple store

atus of this issue and if we could do something to help alleviating it? Thank you! Sebastian (sebotic) -- Sebastian Burgstaller-Muehlbacher, PhD Research Associate Andrew Su Lab MEM-216, Department of Molecular and Experimental Medicine The Scripps Research Institute 10550 North Torrey Pine

Re: [Wikidata] user script to show Wikidata changes in article history

a", but that is > what it stops with. > > Is there anything that has to be changed for other language Wikipedias? > > [1] > > https://de.wikipedia.org/w/index.php?title=Benutzer:Yellowcard/common.js&diff=155881821&oldid=154953646 > > Thanks! > Yellowcard &

Re: [Wikidata] user script to show Wikidata changes in article history

That's a great tool which will alleviate many of the concerns Wikipedians have regarding Wikidata. I did a crude adaptation and translation to make if work on the English Wikipedia. (did not find that somebody else had done this already). https://en.wikipedia.org/wiki/User:Sebotic/wef-history.js I

Re: [Wikidata] Multiple properties/identifiers for the same resource

Thanks for your replies! I like the idea of a resolver service on labs, but I think it cannot solve the issue. e.g. for ChEMBL and IUPHAR (international union of pharmacology), there is no way to guess from the identifier onto the sub-domain this identifier belongs to. For ChEMBL, the pattern is:

[Wikidata] Multiple properties/identifiers for the same resource

Hi everyone, I am lately facing the following problem: There are many (biomedical) resources we import data from, which consist of several parts. And for each of these parts, they use either a different identifier structure, or they use the same identifier structure but with different accession UR

Re: [Wikidata] Wikidata to search chemical compound names

. 2016 om 19:53 schreef Egon Willighagen < > egon.willigha...@gmail.com>: > >> On Mon, Apr 25, 2016 at 7:23 PM, Sebastian Burgstaller >> wrote: >> > A way to achieve this could be to fetch all labels and aliases for all >> > chemical compounds in one query

Re: [Wikidata] Wikidata to search chemical compound names

A way to achieve this could be to fetch all labels and aliases for all chemical compounds in one query and store them locally in your web application. This certainly is only feasible if the number of compounds does not get to big in Wikdiata. Currently, the query takes ~ 6 sec. PREFIX wd:

Re: [Wikidata] Fwd: Undo/rollback of revisions with the Wikidata API

t; There is a fix already, which got stuck on a minor cosmetic issue. I'll merge it > now, should go live in no more than two weeks. But I can try to get it > backported and deployed sooner. > > > Am 11.11.2015 um 20:10 schrieb Sebastian Burgstaller: > > Thanks for your r

Re: [Wikidata] Fwd: Undo/rollback of revisions with the Wikidata API

': 'Direct editing via API is not supported for content ' 'model wikibase-item used by Q5972069'}, 'servedby': 'mw1119'} Undo with the webinterface works, both as a logged in and anonymous user. Will tinker around a little, if I do not find a

[Wikidata] Fwd: Undo/rollback of revisions with the Wikidata API

Hi everyone, Alongside the data model protection discussion, I am now developing a bot which should undo the merges we are facing in the Gene Wiki project. In order for the rollback Wikidata API call to work, I guess our bot account would require special permission for rollback to be able to do t