Re: [Wikidata] [Wikimediaindia-l] New portal on Wikidata: Wikidata:WikiProject India

[Tito Dutta]

Thanks a lot for the email Viswaprabha. I am quite sure that this project
will be really helpful to improve Indic content on Wikidata.


Thanks
Tito Dutta
Note: If I don't reply to your email in 2 days, please feel free to remind
me over email or phone call.

On 9 September 2017 at 03:46, ViswaPrabha (വിശ്വപ്രഭ)  wrote:

>
> Dear Wikimedians,
>
> As the month long country-wide Wikidata Training Tour by Asaf Bartov [*1]
> is in progress through several communities and cities within India, the
> term 'Wikidata' has started rolling out as a new technology buzzword among
> Indian communities and media.
> Choosing the occasion as most befitting, some of us have opened up a new
> WikiProject portal on the Wikidata site, named  WikiProject India.
>
> The page link is https://www.wikidata.org/wiki/Wikidata:WikiProject_India.
>
> This WikiProject is to coordinate the efforts to create, enhance and
> populate the coverage of topics related to India including her history,
> geography, culture, society, people, infrastructure, education,
> demographics and anything related between India and other fields such as
> science, technology, arts, entertainment etc.
>
>
> For now, an indicative list of topics of immediate interest are mentioned
> in the homepage. As the project grow up and get better shape, we can expand
> the scope of the project both vertically and horizontally.
>
> A query library demonstrating some data drilling methods and samples is
> also available there. Together, we can also build up this library to its
> best form and beauty.
>
> An inspiring model to this venture was WikiProject Armenia (
> https://www.wikidata.org/wiki/Wikidata:WikiProject_Armenia), which began
> around a year ago. We may fork and develop upon some of the work show-cased
> there, including the model queries.
> (Building new queries based upon these are quite easy even for a beginner!)
>
> I invite all of you too visit the project homepage.
> https://www.wikidata.org/wiki/Wikidata:WikiProject_India
>
>
> Are you interested to be among the pioneers of this project?
> Do you want to be part of a team that will build up a great national
> database that will eventually help at least one fifth of the world
> population  in  so many ways that we can not even predict now?
>
> If you do, if you are interested in editing and contributing to Wikidata,
> then please sign up and join the project.
>
>
> More questions and suggestions are welcome at the project's talk pages.
>
> Thanks and regards,
>
> User:Viswaprabha
>
>
> *1 . Asaf's Indian path of Wikidata conquest can be seen here:
> https://meta.wikimedia.org/wiki/User:Asaf_(WMF)/2017_Technic
> al_trainings_in_India
>
>
>
>
> ___
> Wikimediaindia-l mailing list
> wikimediaindi...@lists.wikimedia.org
> To unsubscribe from the list / change mailing preferences visit
> https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] New portal on Wikidata: Wikidata:WikiProject India

[വിശ്വപ്രഭ]

Dear Wikimedians,

As the month long country-wide Wikidata Training Tour by Asaf Bartov [*1]
is in progress through several communities and cities within India, the
term 'Wikidata' has started rolling out as a new technology buzzword among
Indian communities and media.
Choosing the occasion as most befitting, some of us have opened up a new
WikiProject portal on the Wikidata site, named  WikiProject India.

The page link is https://www.wikidata.org/wiki/Wikidata:WikiProject_India.

This WikiProject is to coordinate the efforts to create, enhance and
populate the coverage of topics related to India including her history,
geography, culture, society, people, infrastructure, education,
demographics and anything related between India and other fields such as
science, technology, arts, entertainment etc.


For now, an indicative list of topics of immediate interest are mentioned
in the homepage. As the project grow up and get better shape, we can expand
the scope of the project both vertically and horizontally.

A query library demonstrating some data drilling methods and samples is
also available there. Together, we can also build up this library to its
best form and beauty.

An inspiring model to this venture was WikiProject Armenia (
https://www.wikidata.org/wiki/Wikidata:WikiProject_Armenia), which began
around a year ago. We may fork and develop upon some of the work show-cased
there, including the model queries.
(Building new queries based upon these are quite easy even for a beginner!)

I invite all of you too visit the project homepage.
https://www.wikidata.org/wiki/Wikidata:WikiProject_India


Are you interested to be among the pioneers of this project?
Do you want to be part of a team that will build up a great national
database that will eventually help at least one fifth of the world
population  in  so many ways that we can not even predict now?

If you do, if you are interested in editing and contributing to Wikidata,
then please sign up and join the project.


More questions and suggestions are welcome at the project's talk pages.

Thanks and regards,

User:Viswaprabha


*1 . Asaf's Indian path of Wikidata conquest can be seen here:
https://meta.wikimedia.org/wiki/User:Asaf_(WMF)/2017_Technical_trainings_in_India
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Which external identifiers are worth covering?

[Maarten Dammers]

Hi Marco,

On 07-09-17 20:51, Marco Fossati wrote:

Hi everyone,

As a data quality addict, I've been investigating the coverage of 
external identifiers linked to Wikidata items about people.


Given the numbers on SQID [1] and some SPARQL queries [2, 3], it seems 
that even the second most used ID (VIAF) only covers *25%* of people 
items circa.

Then, there is a long tail of IDs that are barely used at all.

So here is my question:
*which external identifiers deserve an effort to achieve exhaustive 
coverage?*
I've been doing this for painters. See 
https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings/Creator_no_authority_control 
and 
https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings/Creator_missing_collection_authority_control 
.


Maarten

___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata-bugs] [Maniphest] [Merged] T143485: [bug] sitelink on Wikidata not removed when page on client is deleted

[matej_suchanek]

matej_suchanek added subscribers: IKhitron, Legoktm, Amire80, eranroz.matej_suchanek merged a task: T175398: Interwiki to page deleted months ago wasn't removed.
TASK DETAILhttps://phabricator.wikimedia.org/T143485EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: matej_suchanekCc: eranroz, Amire80, Legoktm, IKhitron, Liuxinyu970226, Lydia_Pintscher, hoo, Aklapper, Esc3300, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Updated] T175398: Interwiki to page deleted months ago wasn't removed

[matej_suchanek]

matej_suchanek closed this task as a duplicate of T143485: [bug] sitelink on Wikidata not removed when page on client is deleted.
TASK DETAILhttps://phabricator.wikimedia.org/T175398EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: matej_suchanekCc: Legoktm, Amire80, eranroz, IKhitron, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T175398: Interwiki to page deleted months ago wasn't removed

[IKhitron]

IKhitron added a comment.
Thanks.TASK DETAILhttps://phabricator.wikimedia.org/T175398EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: IKhitronCc: Legoktm, Amire80, eranroz, IKhitron, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Updated] T175398: Interwiki to page deleted months ago wasn't removed

[Legoktm]

Legoktm edited projects, added Wikidata; removed Regression, MediaWiki-Interwiki, MediaWiki-Database.Legoktm added a comment.
The page was moved and the interwiki wasn't updated on Wikidata, so putting under #Wikidata .TASK DETAILhttps://phabricator.wikimedia.org/T175398EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: LegoktmCc: Legoktm, Amire80, eranroz, IKhitron, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T175199: Index certain statements for Wikidata items

[Smalyshev]

Smalyshev added a comment.
I'm not sure we should really go as far as indexing all statements, now. Most of them would not be very useful for the search purposes for now, and already served by Query Service. Most useful ones would be those that are legitimately limit the searches for relevant items, which I would imaging mostly are P31/P279. In fact, right now I don't even have much of a use case for using anything but those two, but maybe we'd have it in the future. I think maybe it'd be ok for now yo just index those explicitly mentioned. The idea of using analyzer/filters may be still workable in the future, but I'd postpone it for now.TASK DETAILhttps://phabricator.wikimedia.org/T175199EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: gerritbot, debt, EBernhardson, dcausse, daniel, Aklapper, Smalyshev, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Edited] T175316: Very large jobs posted by Wikidata

[GWicke]

GWicke updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION..."2653965": [6, "Meyers_b9_s0043.jpg"],

(..a few million further page entries...)
},...TASK DETAILhttps://phabricator.wikimedia.org/T175316EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Pchelolo, GWickeCc: daniel, GWicke, Aklapper, Pchelolo, GoranSMilovanovic, QZanden, Izno, Eevans, JAllemandou, mobrovac, Hardikj, Wikidata-bugs, aude, Mbch331, jeremyb___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Created] T175380: Queries with wikibase:statements or wikibase:sitelinks are slow

[Lucas_Werkmeister_WMDE]

Lucas_Werkmeister_WMDE created this task.Lucas_Werkmeister_WMDE added projects: Wikidata, Wikidata-Query-Service.Herald added a subscriber: Aklapper.Herald added a project: Discovery.
TASK DESCRIPTIONI would expect this query to be very efficient:

SELECT ?item ?sitelinks WHERE {
  ?item wikibase:statements ?sitelinks.
}
ORDER BY DESC(?sitelinks)
LIMIT 10

But it times out. The same query with another numeric predicate, like wdt:P2067 (mass), is fairly efficient. I suspect Blazegraph for some reason doesn’t have an index for sorted wikibase:statements (or whatever the equivalent Blazegraph term is)… perhaps because it’s xsd:integer instead of xsd:decimal?

Same situation for wikibase:sitelinks.

Motivation: a Wikipedia user suggested searching for items wtih most sitelinks but no dewiki article. This query should find such items, but also times out:

SELECT ?item ?sitelinks WHERE {
  ?item wikibase:sitelinks ?sitelinks.
  MINUS {
?deArticle schema:about ?item;
   schema:isPartOf .
  }
}
ORDER BY DESC(?sitelinks)
LIMIT 10TASK DETAILhttps://phabricator.wikimedia.org/T175380EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDECc: Aklapper, Smalyshev, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, EBjune, merbst, Avner, debt, Gehel, Jonas, FloNight, Xmlizer, Izno, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T175316: Very large jobs posted by Wikidata

[Pchelolo]

Pchelolo added a comment.

In T175316#3591889, @GWicke wrote:
@Pchelolo, based on our previous conversation about this I am assuming that the bulk of the task is a very large list of pages. Is this correct?


Ye, in the actual event the params.pages array contains millions and millions of items.TASK DETAILhttps://phabricator.wikimedia.org/T175316EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: PcheloloCc: daniel, GWicke, Aklapper, Pchelolo, GoranSMilovanovic, QZanden, Izno, Eevans, JAllemandou, mobrovac, Hardikj, Wikidata-bugs, aude, Mbch331, jeremyb___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Gerard Meijssen]

Hoi,
I understand the tendency to have English labels for items seen as
important. However, there are bots who add labels to many, many languages
as the labels tend to be the same. In my opinion we should encourage the
inclusion of information. Yes, we may get duplicates but having the data
early and being able to expand on them early is of more consequence.

At this time I am adding Dutch people who won literary awards. I add them
in Dutch. There is more relevancy for them in this way.
Thanks,
   GerardM

On 8 September 2017 at 18:33, Jane Darnell  wrote:

> Interesting! I noticed that suddenly a lot more politicians were showing
> up in my queries - have you been adding the occupation=politician property?
> I believe politicians are severely underrepresented on Wikipedia projects
> (except for the top people in the news) so if you have good metadata, then
> yes, it would probably be useful to do a data upload. One caveat is that
> for non-English countries, you need the descriptions and labels for any new
> items in the native language, or else I think we will only end up with
> doubles in the long run. I am not sure if there is any specific projects
> per country-related Wikipedia (I mean like France-French Wikipedia, etc)
> working on politicians, but otherwise you can try to get them active.
>
> On Fri, Sep 8, 2017 at 5:30 PM, Lucy Chambers  wrote:
>
>> Hi folks,
>>
>> Very happy to see this discussion happening.
>>
>> I work on the EveryPolitician project [0] and for several years, we have
>> been mapping official IDs to Wikidata IDs. We have probably half the
>> national legislators in the world mapped this way, and many of the ones
>> we’re missing are because we don’t believe the people have Wikidata items
>> yet.
>>
>> We’d be happy to make the mappings we have available to the Wikidata
>> community but the relevant properties for official identifiers only exist
>> for a handful of countries at the moment[1].
>>
>> EveryPolitician is currently funded by WMF for a related project [2] to
>> find ways to improve the quality of data about politicians in Wikidata. As
>> part of this project, our plan was to work with in-country partners on a
>> case-by-case basis to get these properties created, but in light of this
>> discussion perhaps we should explore creating many more of them in bulk
>> more quickly? Suggestions welcome.
>>
>> Lucy
>>
>> [0] http://everypolitician.org/
>>
>> [1] https://www.wikidata.org/wiki/Wikidata:WikiProject_Parliamen
>> ts#For_members_of_parliament
>>
>> [2] https://meta.wikimedia.org/wiki/Grants:Project/EveryPolitician
>>
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Which external identifiers are worth covering?

[Jane Darnell]

Interesting! I noticed that suddenly a lot more politicians were showing up
in my queries - have you been adding the occupation=politician property? I
believe politicians are severely underrepresented on Wikipedia projects
(except for the top people in the news) so if you have good metadata, then
yes, it would probably be useful to do a data upload. One caveat is that
for non-English countries, you need the descriptions and labels for any new
items in the native language, or else I think we will only end up with
doubles in the long run. I am not sure if there is any specific projects
per country-related Wikipedia (I mean like France-French Wikipedia, etc)
working on politicians, but otherwise you can try to get them active.

On Fri, Sep 8, 2017 at 5:30 PM, Lucy Chambers  wrote:

> Hi folks,
>
> Very happy to see this discussion happening.
>
> I work on the EveryPolitician project [0] and for several years, we have
> been mapping official IDs to Wikidata IDs. We have probably half the
> national legislators in the world mapped this way, and many of the ones
> we’re missing are because we don’t believe the people have Wikidata items
> yet.
>
> We’d be happy to make the mappings we have available to the Wikidata
> community but the relevant properties for official identifiers only exist
> for a handful of countries at the moment[1].
>
> EveryPolitician is currently funded by WMF for a related project [2] to
> find ways to improve the quality of data about politicians in Wikidata. As
> part of this project, our plan was to work with in-country partners on a
> case-by-case basis to get these properties created, but in light of this
> discussion perhaps we should explore creating many more of them in bulk
> more quickly? Suggestions welcome.
>
> Lucy
>
> [0] http://everypolitician.org/
>
> [1] https://www.wikidata.org/wiki/Wikidata:WikiProject_
> Parliaments#For_members_of_parliament
>
> [2] https://meta.wikimedia.org/wiki/Grants:Project/EveryPolitician
>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata-bugs] [Maniphest] [Commented On] T175376: Parser and Lua functions should track changes to 'formatter URL' property

[matej_suchanek]

matej_suchanek added a comment.
Now this is not being tracked at all and we are not able to focus a single property. So the only way is to use an inaccurate aspect (O/X) that tracks all changes to the property, which are irrelevant to individual articles. With C introduction, the aspect will be as simple as C.P1630.TASK DETAILhttps://phabricator.wikimedia.org/T175376EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: matej_suchanekCc: eranroz, matej_suchanek, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Updated] T175376: Parser and Lua functions should track changes to 'formatter URL' property

[eranroz]

eranroz added a comment.
@matej_suchanek , this is good point. I think it is not related to usage aspect C directly. Can you please elaborate ?
Currently either someone access it explicitly (getEntity(P214)) or implicitly using formatValue and similar stuff. I think it is/should be handled in UsageTrackingSnakFormatter.

PS: C is going to be evaluated soon in  https://gerrit.wikimedia.org/r/#/c/375544/  (if this could have any negative impact please -1 there)TASK DETAILhttps://phabricator.wikimedia.org/T175376EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: eranrozCc: eranroz, matej_suchanek, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Lucy Chambers]

Hi folks,

Very happy to see this discussion happening.

I work on the EveryPolitician project [0] and for several years, we have
been mapping official IDs to Wikidata IDs. We have probably half the
national legislators in the world mapped this way, and many of the ones
we’re missing are because we don’t believe the people have Wikidata items
yet.

We’d be happy to make the mappings we have available to the Wikidata
community but the relevant properties for official identifiers only exist
for a handful of countries at the moment[1].

EveryPolitician is currently funded by WMF for a related project [2] to
find ways to improve the quality of data about politicians in Wikidata. As
part of this project, our plan was to work with in-country partners on a
case-by-case basis to get these properties created, but in light of this
discussion perhaps we should explore creating many more of them in bulk
more quickly? Suggestions welcome.

Lucy

[0] http://everypolitician.org/

[1]
https://www.wikidata.org/wiki/Wikidata:WikiProject_Parliaments#For_members_of_parliament

[2] https://meta.wikimedia.org/wiki/Grants:Project/EveryPolitician
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata-bugs] [Maniphest] [Created] T175376: Parser and Lua functions should track changes to 'formatter URL' property

[matej_suchanek]

matej_suchanek created this task.matej_suchanek added projects: Wikidata, MediaWiki-extensions-WikibaseClient.Herald added a subscriber: Aklapper.
TASK DESCRIPTIONThis may happen after the usage aspect C is deployed. It will require some more thinking, though, since the option formatterUrlProperty is only available to the repository.TASK DETAILhttps://phabricator.wikimedia.org/T175376EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: matej_suchanekCc: matej_suchanek, Aklapper, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Updated] T175370: Track incompatible (mutually exclusive) constraints

[Lucas_Werkmeister_WMDE]

Lucas_Werkmeister_WMDE added a project: Wikibase-Quality.
TASK DETAILhttps://phabricator.wikimedia.org/T175370EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDECc: matej_suchanek, Aklapper, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, Agabi10, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Created] T175370: Track incompatible (mutually exclusive) constraints

[matej_suchanek]

matej_suchanek created this task.matej_suchanek added a project: Wikibase-Quality-Constraints.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONSample (A,B,C are properties):


A is an inverse to B and conflicts with C. B requires items with A to also have C.
A requires B and C, whereas B conflicts with C.
...


This can be tracked with SPARQL but I suppose the extension could also track and report this directly on statements like other problems with constraint definitions.TASK DETAILhttps://phabricator.wikimedia.org/T175370EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: matej_suchanekCc: matej_suchanek, Aklapper, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, Agabi10, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Updated] T175316: Very large jobs posted by Wikidata

[mobrovac]

mobrovac edited projects, added Services (designing), EventBus; removed Services (doing).Herald added a project: Analytics.
TASK DETAILhttps://phabricator.wikimedia.org/T175316EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Pchelolo, mobrovacCc: daniel, GWicke, Aklapper, Pchelolo, GoranSMilovanovic, QZanden, Izno, Eevans, JAllemandou, mobrovac, Hardikj, Wikidata-bugs, aude, Mbch331, jeremyb___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T154555: Special:SetSiteLink, other SpecialModifyEntity subclasses open master connection on GET

[gerritbot]

gerritbot added a comment.
Change 376700 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Use master when needed in EditEntity::getLatestRevision()

https://gerrit.wikimedia.org/r/376700TASK DETAILhttps://phabricator.wikimedia.org/T154555EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Ladsgroup, gerritbotCc: PokestarFan, aude, Ladsgroup, Lydia_Pintscher, Amire80, daniel, Johan, Glaisher, Nemo_bis, Gilles, PleaseStand, Krenair, Joe, aaron, gerritbot, MZMcBride, Aklapper, Catrope, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, Mbch331, Jay8g___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T172246: Support rollout of editing wikidata descriptions on Android for en.wp

[Elitre]

Elitre added a comment.
The announcements were posted days ago at en.wp and Wikidata (Wikidata staff was also pinged about this as usual). We're keeping an eye on the conversation and addressing feedback as it comes.TASK DETAILhttps://phabricator.wikimedia.org/T172246EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: ElitreCc: PokestarFan, Aklapper, JKatzWMF, Dbrant, Qgil, Trizek-WMF, Tbayer, Fjalapeno, Lea_Lacroix_WMDE, He7d3r, gerritbot, Stashbot, Elitre, SandraF_WMF, GoranSMilovanovic, nickisverygood, Ivana_Isadora, QZanden, Designsbydavesconcepts, Serumulapiet, Jseddon, donaldepig, FloNight, Izno, Wikidata-bugs, Base, aude, Mbch331, Keegan___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Andy Mabbett]

On 7 September 2017 at 19:51, Marco Fossati  wrote:

> external identifiers linked to Wikidata items about people.

I'll take this as an invitation to remind everyone about ORCID iDs ;-)

See:

   https://www.wikidata.org/wiki/Wikidata:ORCID

and:

   https://en.wikipedia.org/wiki/Wikipedia:ORCID

Not only is this an identifier for people who often have no other ID
for us to use, but it is one that they can register for, and manage,
themselves.

So we can help ourselves, by encouraging the people we write about to
register for, and use, one. This is especially true (but not limited
to) all the authors of scientific papers which we are currently adding
to Wikidata.

However, although an ORCID iD is free to register and use, and ORCID
is an open source project, run by a non-profit foundation, there has
been some resistance, from a few noisy individuals, to us doing this.
The German Wikipedia community has so far, refused to include ORCID
iDs in its "Normdaten" ("Authority control") template.

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata-bugs] [Maniphest] [Commented On] T173742: [Story] Editable Grammatical Feature of a Form (presistent)

[gerritbot]

gerritbot added a comment.
Change 376705 had a related patch set uploaded (by Aleksey Bekh-Ivanov (WMDE); owner: Aleksey Bekh-Ivanov (WMDE)):
[mediawiki/extensions/WikibaseLexeme@master] Use FormSet inside of the Lexeme class

https://gerrit.wikimedia.org/r/376705TASK DETAILhttps://phabricator.wikimedia.org/T173742EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Aleksey_WMDE, gerritbotCc: gerritbot, Jonas, Aklapper, daniel, Lordiis, Cinemantique, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Darkdadaah, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T173742: [Story] Editable Grammatical Feature of a Form (presistent)

[gerritbot]

gerritbot added a comment.
Change 376704 had a related patch set uploaded (by Aleksey Bekh-Ivanov (WMDE); owner: Aleksey Bekh-Ivanov (WMDE)):
[mediawiki/extensions/WikibaseLexeme@master] [WIP] Add form API module

https://gerrit.wikimedia.org/r/376704TASK DETAILhttps://phabricator.wikimedia.org/T173742EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Aleksey_WMDE, gerritbotCc: gerritbot, Jonas, Aklapper, daniel, Lordiis, Cinemantique, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Darkdadaah, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T173742: [Story] Editable Grammatical Feature of a Form (presistent)

[gerritbot]

gerritbot added a comment.
Change 376703 had a related patch set uploaded (by Aleksey Bekh-Ivanov (WMDE); owner: Aleksey Bekh-Ivanov (WMDE)):
[mediawiki/extensions/WikibaseLexeme@master] Add assertions to ensure $nextFormId correctness in Lexeme

https://gerrit.wikimedia.org/r/376703TASK DETAILhttps://phabricator.wikimedia.org/T173742EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Aleksey_WMDE, gerritbotCc: gerritbot, Jonas, Aklapper, daniel, Lordiis, Cinemantique, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Darkdadaah, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Osma Suominen]

Somewhat related to this discussion is the coli-conc project, which 
collects statistics about KOS-type (thesaurus, authority file etc.) 
identifier links in Wikidata:


http://coli-conc.gbv.de/concordances/wikidata/

You can also find statistics about indirect mappings, from one KOS via 
Wikidata to another KOS.


-Osma

Magnus Manske kirjoitti 08.09.2017 klo 13:01:
Is anyone working on an "auto-resolve" bot? If you have VIAF (but 
nothing else), you can resolve other identifiers via the VIAF site; 
similarly, if you have only GND, you could try to reverse-lookup VIAF.


I think a list of items that have zero external identifiers, ordered by 
"importance" (incoming wikidata links, number of statements etc) would 
also be helpful.


On Fri, Sep 8, 2017 at 10:52 AM Jane Darnell > wrote:


As a basic rule for "which external identifiers are worth covering",
I would begin with any  national identifiers we have for people
(politicians, artists, writers, theologians, scientists, etc), then
national identifiers for organizations (government-related,
GNP-related businesses, nonprofits, educational institutions, etc),
then national identifiers for places (census-defined population
centers, battle-scenes, etc)

In my opnion, the question should not be "which identifier has the
most coverage" but "which items have the most identifiers"


On Thu, Sep 7, 2017 at 9:26 PM, Andrew Gray
> wrote:

Hi Marco,

I guess this depends what you mean by "exhaustive". Exhaustive
in that
every Wikidata item has ID X, or exhaustive in that we have every
instance of ID X in Wikidata?

The first is probably not going to happen, as the vast majority of
external identifiers have a defined scope for what they
identify. Some
are pretty broad - VIAF is essentially "everyone who exists in a
library catalogue as an author or subject" - but still have a limit.
We're never really going to reach a situation where there is a
single
identifier type that covers everyone, unless we're linking across to
another Wikidata-type comprehensive knowledgebase, and even then
we'd
need to ensure we're in a position where they already cover
everything
in Wikidata.

The second can (and has) been done - the largest one I know of
offhand
for people is the Oxford DNB (60k items) but for non-people we have
complete coverage of eg Swedish district codes, P1841 (160k items).
It's a bit of a slog to get these completed and then maintained,
since
the last 5-10% tend to be more challenging complicated cases,
but one
or two determined people can make it happen. And of course it's not
appropriate for many identifiers, as they may issue IDs for things
that we don't intend to have in Wikidata, so we will never
completely
cover them.

I should quickly plug the "expected completeness" property which is
really useful for identifiers - P2429 - as this can quickly show
whether something is a) completely on Wikidata; b) not complete yet
but eventually might be; or c) probably never will be. Not very
widely
rolled out yet, though...

Andrew.


On 7 September 2017 at 19:51, Marco Fossati
> wrote:
 > Hi everyone,
 >
 > As a data quality addict, I've been investigating the
coverage of external
 > identifiers linked to Wikidata items about people.
 >
 > Given the numbers on SQID [1] and some SPARQL queries [2, 3],
it seems that
 > even the second most used ID (VIAF) only covers *25%* of
people items circa.
 > Then, there is a long tail of IDs that are barely used at all.
 >
 > So here is my question:
 > *which external identifiers deserve an effort to achieve
exhaustive
 > coverage?*
 >
 > Looking forward to your valuable feedback.
 > Cheers,
 >
 > Marco
 >
 > [1] https://tools.wmflabs.org/sqid/#/browse?type=properties
"Select
 > datatype" set to "ExternalId", "Used for class" set to "human Q5"
 > [2] total people: http://tinyurl.com/ybvcm5uw
 > [3] people with a VIAF link: http://tinyurl.com/ya6dnpr7
 >
 > ___
 > Wikidata mailing list
 > Wikidata@lists.wikimedia.org

 > https://lists.wikimedia.org/mailman/listinfo/wikidata



--
- Andrew Gray
and...@generalist.org.uk 

[Wikidata-bugs] [Maniphest] [Commented On] T165578: [Story] New datatype for referencing Lexemes

[gerritbot]

gerritbot added a comment.
Change 357796 abandoned by Ladsgroup:
[Code experiment] What needs to be done to make lexeme datatype work

https://gerrit.wikimedia.org/r/357796TASK DETAILhttps://phabricator.wikimedia.org/T165578EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_Pintscher, gerritbotCc: Ladsgroup, WMDE-leszek, gerritbot, Aklapper, Lydia_Pintscher, Lordiis, Cinemantique, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Darkdadaah, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Antonin Delpeuch (lists)]

In general, I think it would be great to store inside Wikidata the graph
of relations between identifiers. Something like:

VIAF linksTo ISNI
VIAF linksTo GND
…
GRID linksTo ISNI
arXiv linksTo DOI

Last time I looked, there was no simple way to do that. So for
WikiProject Universities we have used a manual approach:
https://www.wikidata.org/wiki/Wikidata:WikiProject_Universities/External_databases

Antonin

On 08/09/2017 11:01, Magnus Manske wrote:
> Is anyone working on an "auto-resolve" bot? If you have VIAF (but
> nothing else), you can resolve other identifiers via the VIAF site;
> similarly, if you have only GND, you could try to reverse-lookup VIAF.
> 
> I think a list of items that have zero external identifiers, ordered by
> "importance" (incoming wikidata links, number of statements etc) would
> also be helpful.
> 
> On Fri, Sep 8, 2017 at 10:52 AM Jane Darnell  > wrote:
> 
> As a basic rule for "which external identifiers are worth covering",
> I would begin with any  national identifiers we have for people
> (politicians, artists, writers, theologians, scientists, etc), then
> national identifiers for organizations (government-related,
> GNP-related businesses, nonprofits, educational institutions, etc),
> then national identifiers for places (census-defined population
> centers, battle-scenes, etc)
> 
> In my opnion, the question should not be "which identifier has the
> most coverage" but "which items have the most identifiers"
> 
> 
> On Thu, Sep 7, 2017 at 9:26 PM, Andrew Gray
> > wrote:
> 
> Hi Marco,
> 
> I guess this depends what you mean by "exhaustive". Exhaustive
> in that
> every Wikidata item has ID X, or exhaustive in that we have every
> instance of ID X in Wikidata?
> 
> The first is probably not going to happen, as the vast majority of
> external identifiers have a defined scope for what they
> identify. Some
> are pretty broad - VIAF is essentially "everyone who exists in a
> library catalogue as an author or subject" - but still have a limit.
> We're never really going to reach a situation where there is a
> single
> identifier type that covers everyone, unless we're linking across to
> another Wikidata-type comprehensive knowledgebase, and even then
> we'd
> need to ensure we're in a position where they already cover
> everything
> in Wikidata.
> 
> The second can (and has) been done - the largest one I know of
> offhand
> for people is the Oxford DNB (60k items) but for non-people we have
> complete coverage of eg Swedish district codes, P1841 (160k items).
> It's a bit of a slog to get these completed and then maintained,
> since
> the last 5-10% tend to be more challenging complicated cases,
> but one
> or two determined people can make it happen. And of course it's not
> appropriate for many identifiers, as they may issue IDs for things
> that we don't intend to have in Wikidata, so we will never
> completely
> cover them.
> 
> I should quickly plug the "expected completeness" property which is
> really useful for identifiers - P2429 - as this can quickly show
> whether something is a) completely on Wikidata; b) not complete yet
> but eventually might be; or c) probably never will be. Not very
> widely
> rolled out yet, though...
> 
> Andrew.
> 
> 
> On 7 September 2017 at 19:51, Marco Fossati
> > wrote:
> > Hi everyone,
> >
> > As a data quality addict, I've been investigating the coverage
> of external
> > identifiers linked to Wikidata items about people.
> >
> > Given the numbers on SQID [1] and some SPARQL queries [2, 3],
> it seems that
> > even the second most used ID (VIAF) only covers *25%* of
> people items circa.
> > Then, there is a long tail of IDs that are barely used at all.
> >
> > So here is my question:
> > *which external identifiers deserve an effort to achieve
> exhaustive
> > coverage?*
> >
> > Looking forward to your valuable feedback.
> > Cheers,
> >
> > Marco
> >
> > [1] https://tools.wmflabs.org/sqid/#/browse?type=properties
> "Select
> > datatype" set to "ExternalId", "Used for class" set to "human Q5"
> > [2] total people: http://tinyurl.com/ybvcm5uw
> > [3] people with a VIAF link: http://tinyurl.com/ya6dnpr7
> >
> > ___
> > Wikidata mailing list
>  

[Wikidata-bugs] [Maniphest] [Commented On] T154555: Special:SetSiteLink, other SpecialModifyEntity subclasses open master connection on GET

[gerritbot]

gerritbot added a comment.
Change 376700 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Use master when needed in EditEntity::getLatestRevision()

https://gerrit.wikimedia.org/r/376700TASK DETAILhttps://phabricator.wikimedia.org/T154555EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Ladsgroup, gerritbotCc: PokestarFan, aude, Ladsgroup, Lydia_Pintscher, Amire80, daniel, Johan, Glaisher, Nemo_bis, Gilles, PleaseStand, Krenair, Joe, aaron, gerritbot, MZMcBride, Aklapper, Catrope, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Izno, Wikidata-bugs, Mbch331, Jay8g___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Re: [Wikidata] Which external identifiers are worth covering?

[Magnus Manske]

Is anyone working on an "auto-resolve" bot? If you have VIAF (but nothing
else), you can resolve other identifiers via the VIAF site; similarly, if
you have only GND, you could try to reverse-lookup VIAF.

I think a list of items that have zero external identifiers, ordered by
"importance" (incoming wikidata links, number of statements etc) would also
be helpful.

On Fri, Sep 8, 2017 at 10:52 AM Jane Darnell  wrote:

> As a basic rule for "which external identifiers are worth covering", I
> would begin with any  national identifiers we have for people (politicians,
> artists, writers, theologians, scientists, etc), then national identifiers
> for organizations (government-related, GNP-related businesses, nonprofits,
> educational institutions, etc), then national identifiers for places
> (census-defined population centers, battle-scenes, etc)
>
> In my opnion, the question should not be "which identifier has the most
> coverage" but "which items have the most identifiers"
>
>
> On Thu, Sep 7, 2017 at 9:26 PM, Andrew Gray 
> wrote:
>
>> Hi Marco,
>>
>> I guess this depends what you mean by "exhaustive". Exhaustive in that
>> every Wikidata item has ID X, or exhaustive in that we have every
>> instance of ID X in Wikidata?
>>
>> The first is probably not going to happen, as the vast majority of
>> external identifiers have a defined scope for what they identify. Some
>> are pretty broad - VIAF is essentially "everyone who exists in a
>> library catalogue as an author or subject" - but still have a limit.
>> We're never really going to reach a situation where there is a single
>> identifier type that covers everyone, unless we're linking across to
>> another Wikidata-type comprehensive knowledgebase, and even then we'd
>> need to ensure we're in a position where they already cover everything
>> in Wikidata.
>>
>> The second can (and has) been done - the largest one I know of offhand
>> for people is the Oxford DNB (60k items) but for non-people we have
>> complete coverage of eg Swedish district codes, P1841 (160k items).
>> It's a bit of a slog to get these completed and then maintained, since
>> the last 5-10% tend to be more challenging complicated cases, but one
>> or two determined people can make it happen. And of course it's not
>> appropriate for many identifiers, as they may issue IDs for things
>> that we don't intend to have in Wikidata, so we will never completely
>> cover them.
>>
>> I should quickly plug the "expected completeness" property which is
>> really useful for identifiers - P2429 - as this can quickly show
>> whether something is a) completely on Wikidata; b) not complete yet
>> but eventually might be; or c) probably never will be. Not very widely
>> rolled out yet, though...
>>
>> Andrew.
>>
>>
>> On 7 September 2017 at 19:51, Marco Fossati 
>> wrote:
>> > Hi everyone,
>> >
>> > As a data quality addict, I've been investigating the coverage of
>> external
>> > identifiers linked to Wikidata items about people.
>> >
>> > Given the numbers on SQID [1] and some SPARQL queries [2, 3], it seems
>> that
>> > even the second most used ID (VIAF) only covers *25%* of people items
>> circa.
>> > Then, there is a long tail of IDs that are barely used at all.
>> >
>> > So here is my question:
>> > *which external identifiers deserve an effort to achieve exhaustive
>> > coverage?*
>> >
>> > Looking forward to your valuable feedback.
>> > Cheers,
>> >
>> > Marco
>> >
>> > [1] https://tools.wmflabs.org/sqid/#/browse?type=properties "Select
>> > datatype" set to "ExternalId", "Used for class" set to "human Q5"
>> > [2] total people: http://tinyurl.com/ybvcm5uw
>> > [3] people with a VIAF link: http://tinyurl.com/ya6dnpr7
>> >
>> > ___
>> > Wikidata mailing list
>> > Wikidata@lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>>
>> --
>> - Andrew Gray
>>   and...@generalist.org.uk
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Which external identifiers are worth covering?

[Jane Darnell]

As a basic rule for "which external identifiers are worth covering", I
would begin with any  national identifiers we have for people (politicians,
artists, writers, theologians, scientists, etc), then national identifiers
for organizations (government-related, GNP-related businesses, nonprofits,
educational institutions, etc), then national identifiers for places
(census-defined population centers, battle-scenes, etc)

In my opnion, the question should not be "which identifier has the most
coverage" but "which items have the most identifiers"


On Thu, Sep 7, 2017 at 9:26 PM, Andrew Gray 
wrote:

> Hi Marco,
>
> I guess this depends what you mean by "exhaustive". Exhaustive in that
> every Wikidata item has ID X, or exhaustive in that we have every
> instance of ID X in Wikidata?
>
> The first is probably not going to happen, as the vast majority of
> external identifiers have a defined scope for what they identify. Some
> are pretty broad - VIAF is essentially "everyone who exists in a
> library catalogue as an author or subject" - but still have a limit.
> We're never really going to reach a situation where there is a single
> identifier type that covers everyone, unless we're linking across to
> another Wikidata-type comprehensive knowledgebase, and even then we'd
> need to ensure we're in a position where they already cover everything
> in Wikidata.
>
> The second can (and has) been done - the largest one I know of offhand
> for people is the Oxford DNB (60k items) but for non-people we have
> complete coverage of eg Swedish district codes, P1841 (160k items).
> It's a bit of a slog to get these completed and then maintained, since
> the last 5-10% tend to be more challenging complicated cases, but one
> or two determined people can make it happen. And of course it's not
> appropriate for many identifiers, as they may issue IDs for things
> that we don't intend to have in Wikidata, so we will never completely
> cover them.
>
> I should quickly plug the "expected completeness" property which is
> really useful for identifiers - P2429 - as this can quickly show
> whether something is a) completely on Wikidata; b) not complete yet
> but eventually might be; or c) probably never will be. Not very widely
> rolled out yet, though...
>
> Andrew.
>
>
> On 7 September 2017 at 19:51, Marco Fossati  wrote:
> > Hi everyone,
> >
> > As a data quality addict, I've been investigating the coverage of
> external
> > identifiers linked to Wikidata items about people.
> >
> > Given the numbers on SQID [1] and some SPARQL queries [2, 3], it seems
> that
> > even the second most used ID (VIAF) only covers *25%* of people items
> circa.
> > Then, there is a long tail of IDs that are barely used at all.
> >
> > So here is my question:
> > *which external identifiers deserve an effort to achieve exhaustive
> > coverage?*
> >
> > Looking forward to your valuable feedback.
> > Cheers,
> >
> > Marco
> >
> > [1] https://tools.wmflabs.org/sqid/#/browse?type=properties "Select
> > datatype" set to "ExternalId", "Used for class" set to "human Q5"
> > [2] total people: http://tinyurl.com/ybvcm5uw
> > [3] people with a VIAF link: http://tinyurl.com/ya6dnpr7
> >
> > ___
> > Wikidata mailing list
> > Wikidata@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
>
> --
> - Andrew Gray
>   and...@generalist.org.uk
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata-bugs] [Maniphest] [Updated] T175199: Index certain statements for Wikidata items

[EBernhardson]

EBernhardson added a comment.
It's possible to hack something together by using pattern capture filter to either capture the letter P, or capture the full line if the P-id is one we accept. Then add a stop words filter to strip out the P tokens.  TBH that's pretty messy though: P5976

Provided the relationships ["P31:Q54321", "P1:Q1234", "P31:Q7654", "P42:Q"] and a keep for P31 and P42  this returns:

{
  "relationships.properties": [
"P31",
"P42"
  ],
  "relationships": [
"P31:Q54321",
"P31:Q7654",
"P42:Q"
  ]
}TASK DETAILhttps://phabricator.wikimedia.org/T175199EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev, EBernhardsonCc: gerritbot, debt, EBernhardson, dcausse, daniel, Aklapper, Smalyshev, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T175153: Constraints gadget: change help button to normal link

[gerritbot]

gerritbot added a comment.
Change 376538 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Add margin-left to gadget help link

https://gerrit.wikimedia.org/r/376538TASK DETAILhttps://phabricator.wikimedia.org/T175153EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDE, gerritbotCc: Lydia_Pintscher, thiemowmde, gerritbot, WMDE-Design, Hanna_Petruschat_WMDE, Lucas_Werkmeister_WMDE, Aklapper, Jan_Dittrich, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Lewizho99, Maathavan, Agabi10, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

[Wikidata-bugs] [Maniphest] [Commented On] T175199: Index certain statements for Wikidata items

[dcausse]

dcausse added a comment.
maybe custom analysis components in the extra plugin would make this easier?
Unless we have some objections to making wikibase dependent on the wmf elastic plugins?TASK DETAILhttps://phabricator.wikimedia.org/T175199EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev, dcausseCc: gerritbot, debt, EBernhardson, dcausse, daniel, Aklapper, Smalyshev, Lordiis, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, Lewizho99, Maathavan, Izno, Wikidata-bugs, aude, Mbch331___
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs