[Wikidata-bugs] [Maniphest] T297995: Remove authentication from Wikimedia Commons Query Services (WCQS)

Husky added a comment. In T297995#8872458 <https://phabricator.wikimedia.org/T297995#8872458>, @Legoktm wrote: > My impression from speaking with multiple people at the hackathon is that the authentication requirement is a barrier for people to even use the service in the fi

[Wikidata-bugs] [Maniphest] T230315: [XL] Create a way to see and add references to structured data on Commons (MediaInfo) statements

Husky added a comment. Seems this is live on production. Great to see this finally working! TASK DETAIL https://phabricator.wikimedia.org/T230315 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: matthiasmullie, Husky Cc: Etonkovidova

[Wikidata] Re: Activities - because we all need to find something to do sometimes :-)

Hey Thad, an 'activity' or 'activities' property would seem a bit broad to be me, and hard to properly define. Compared to the 'things to do' results on the search engines you mention, this would be very hard to replicate with a regular property on Wikidata. What is the criteria for a 'popular

[Wikidata-bugs] [Maniphest] T290300: Serve WCQS Sparql endpoint through api.wikimedia.org with OAuth 2

Husky added a comment. > Because it prevents creating client only solutions and requests would need to be routed via proxy which would do the authentication. This would increase overall complexity. +1. We're in a really fortunate position to being one of the very few large websi

[Wikidata] Re: Wikidata Query Service scaling update Aug 2021

tication layer, but it would be a shame. The Wikimedia projects API's (i'm sharing the query service among those) are one of the very few large-scale API's with useful data that don't need any kind of authentication. Making it really useful to teach to students or people just dabbling in writing software.

[Wikidata] Re: Fwd: wikidata mailing list migration complete

OMG, finally a website with an archive that doesn't look like we're still in the good old days of dial-up modems and Netscape Navigator. Thanks for the hard work! -- Hay On Mon, May 10, 2021 at 7:36 PM Federico Leva (Nemo) wrote: > > FYI > > No action required, but feel free to click the links

Re: [Wikidata] We built two tools to help editors get a more complete picture of the data quality on Wikidata

Hey Mohammed, thanks for sharing! I've used the Item Quality Evaluator and it seems very useful indeed. I like the fact that the lowest ranking items are put on top, so they can get the TLC they deserve. Also, i didn't realise that the full query editor was integrated in the SPARQL field, a

[Wikidata-bugs] [Maniphest] T230315: Allow adding references to structured data (MediaInfo) statements

Husky added a comment. Copying my comment from the duplicate task here about why this would be very useful (apart from machine learning): - References on who's depicted on a photograph or painting. For example, most sources say the model on the Mona Lisa is Lisa del Giocondo, but some

Re: [Wikidata] New drill-down site for Wikidata: Wikidata Walkabout

Hey Yaron, comments inline. On Thu, Sep 24, 2020 at 3:15 PM Yaron Koren wrote: > - I agree that it would be great to have autocompletion within the "select > class" input. Similarly, I agree that it would be great to have free text > inputs to let users specify arbitrary values when choosing

Re: [Wikidata] New drill-down site for Wikidata: Wikidata Walkabout

Hey Yaron and Sahaj, awesome, i've been thinking about building something like this before, and it's nice that somebody finally did just that :) A couple of things I noticed: * I understand that you're trying to hide Q/P-numbers (which I think is a good idea), but you still need them for the

Re: [Wikidata] Wikimedia Commons Query Service (WCQS)

On Fri, Jul 24, 2020 at 10:39 AM Guillaume Lederrey wrote: > I've created https://phabricator.wikimedia.org/T258769 to track this request. Great, thanks for doing that. I've added an example query (https://tinyurl.com/y26mtate) of how things are currently done. > It is unlikely that we'll be

[Wikidata-bugs] [Maniphest] T258769: ImageGrid for WCQS

Husky added a comment. See https://tinyurl.com/y26mtate for an example of how this is currently done. Given that items returned will virtually always be images (or at least things that can be represented as images) i guess it makes sense that every query always returns images and maybe uses

Re: [Wikidata] Wikimedia Commons Query Service (WCQS)

Awesome, i'm really happy we finally have at least a start of a functioning query service. For now, the two things that i guess would be helpful for most query writers: 1) A way to make ImageGrid work without resorting to the clunky Special:FilePath hack 2) A nicer way to query Wikidata

Re: [Wikidata] New URL for OpenRefine reconciliation service

Cheers, this seems to work again for me! -- Hay On Wed, Jul 8, 2020 at 2:10 PM Antonin Delpeuch (lists) wrote: > > Hi, > > This change is now live! If you cannot reconcile to Wikidata anymore, > delete the Wikidata reconciliation service and add it again with the new > URL: > >

[Wikidata-bugs] [Maniphest] [Commented On] T221921: Provision search endpoint for SDC. Requirements from Product Team.

Husky added a comment. @CBogen cool, thanks for the update. Really looking forward to be able to test something! TASK DETAIL https://phabricator.wikimedia.org/T221921 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Husky Cc: David_Haskiya_WMSE

[Wikidata-bugs] [Maniphest] [Commented On] T252079: mw.wikibase.getLabelByLang('Q1', 'en') returning nil today

Husky added a comment. I don't see the same things that @Dominicbm sees, so this might have been fixed by the rollback? F31806065: Screenshot 2020-05-07 at 11.40.23.png <https://phabricator.wikimedia.org/F31806065> TASK DETAIL https://phabricator.wikimedia.org/T252079

[Wikidata-bugs] [Maniphest] [Commented On] T221921: Provision search endpoint for SDC. Requirements from Product Team.

Husky added a comment. In T221921#6103577 <https://phabricator.wikimedia.org/T221921#6103577>, @Spinster wrote: > As for a SPARQL endpoint being challenging for many end users from an UX perspective - I would say: don't underestimate our end users and community. +

Re: [Wikidata] Help with "depends on hardware" Property Proposal

www.linkedin.com/in/thadguidry/ > > > On Fri, Apr 24, 2020 at 6:40 PM Hay (Husky) wrote: >> >> Hey Thad, >> interesting question. Maybe P400 (platform) might work? This is mostly >> used for things like 'Playstation 4' or 'iOS', but i think processor >> architec

Re: [Wikidata] Help with "depends on hardware" Property Proposal

Hey Thad, interesting question. Maybe P400 (platform) might work? This is mostly used for things like 'Playstation 4' or 'iOS', but i think processor architecture could be valid there as well. Kind regards, -- Hay On Sat, Apr 25, 2020 at 12:11 AM Thad Guidry wrote: > > With application Q166142

Re: [Wikidata] Working with time-series data (for COVID)

Hey SJ, do you have a specific example that might be useful to look at? -- Hay On Fri, Apr 10, 2020 at 4:14 PM Samuel Klein wrote: > > There are many highly used templates on WP with time-series data about COVID > spread: cases, tests, health outcomes, by region + per day. Each cell has a >

[Wikidata-bugs] [Maniphest] [Commented On] T221921: Provision search endpoint for SDC. Requirements from Product Team.

Husky added a comment. In T221921#5973902 <https://phabricator.wikimedia.org/T221921#5973902>, @Jarekt wrote: > That would be great. I think the frustration is due to expectations management. +1. It's pretty hard to stay excited about SDoC when there's no proper way

[Wikidata-bugs] [Maniphest] [Commented On] T141602: [Objective Fiscal 19-20/Q2] (9) Provide a Proof of Concept SPARQL endpoint in support of SDoC project (stretch)

Husky added a comment. @Gehel, thanks for your response! TASK DETAIL https://phabricator.wikimedia.org/T141602 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Husky Cc: Lea_Lacroix_WMDE, PDrouin-WMF, Gehel, Nicolas_Raoul, Mmarx, Multichill

[Wikidata-bugs] [Maniphest] [Changed Subscribers] T141602: [Objective Fiscal 19-20/Q2] (9) Provide a Proof of Concept SPARQL endpoint in support of SDoC project (stretch)

Husky added a subscriber: Lea_Lacroix_WMDE. Husky added a comment. @Jarekt afaik this is only a proof of concept. However, the data does seem to be updated (previously it only had the data from april or so). I don't know who is currently maintaining the beta, but maybe @Lea_Lacroix_WMDE

[Wikidata-bugs] [Maniphest] [Commented On] T181062: Adapt QuickStatements2 to be able to work with structured data on Commons as well

Husky added a comment. The tool mentioned by @Spinster above is done and working over here: https://tools.wmflabs.org/hay/minefield/ It also supports PagePile ids. TASK DETAIL https://phabricator.wikimedia.org/T181062 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings

[Wikidata-bugs] [Maniphest] [Commented On] T238443: Add P180 (Depicts) and P6243 (Digital representation of) structured data to Commons files representing artworks by Jakob Smits

Husky added a comment. Well, the tool is done and working: https://tools.wmflabs.org/hay/minefield/ TASK DETAIL https://phabricator.wikimedia.org/T238443 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Husky Cc: Husky, SandraF_WMF, Salgo60

[Wikidata-bugs] [Maniphest] [Updated] T141602: [Objective Fiscal 19-20/Q2] (9) Provide a Proof of Concept SPARQL endpoint in support of SDoC project (stretch)

Husky added a comment. Hey, as a proof of concept, i've adapted my VizQuery <https://tools.wmflabs.org/hay/vizquery/> tool to use the beta endpoint <https://sdcquery.wmflabs.org/>. You can find the experimental VizQuery version over here <https://tools.wmflabs.o

[Wikidata-bugs] [Maniphest] [Commented On] T216601: Allow download of Wikidata query results in GPS-friendly format(s)

Husky added a comment. It would also be really nice if this could export to either GeoJSON or TopoJSON, because it makes it a lot easier to integrate query results in visualisation tools. For example, Vega-lite maps <https://vega.github.io/vega-lite/examples/geo_layer.html>. TASK

[Wikidata-bugs] [Maniphest] [Commented On] T208105: Query wikidata based on wikimedia pageviews

Husky added a comment. Try this: https://meta.wikimedia.org/wiki/PetScan#Get_the_sitelinks_for_a_certain_project_from_a_SPARQL_queryTASK DETAILhttps://phabricator.wikimedia.org/T208105EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Arybolab, HuskyCc: Husky

[Wikidata-bugs] [Maniphest] [Commented On] T208036: Scrape chemical names and data for WikiData from ChemSpider

Husky added a comment. @S9a8m let me know if you need some assistance with scraping, i can help.TASK DETAILhttps://phabricator.wikimedia.org/T208036EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: HuskyCc: Husky, Laffano, S9a8m, Vemonet, A_ka_es, Dinadineke

[Wikidata-bugs] [Maniphest] [Created] T208042: Some WDQS servers might not be up to date

Husky created this task.Husky added a project: Wikidata-Query-Service.Restricted Application added a subscriber: Aklapper.Restricted Application added a project: Wikidata. TASK DESCRIPTIONWith some queries i'm not seeing all data that should be available for an item. For example, compare

Re: [Wikidata] Number of properties

If you also want to see a short description and filter them you could use my tool: https://tools.wmflabs.org/hay/propbrowse/ We're at 5.299 now. -- Hay On Fri, Sep 21, 2018 at 9:21 PM Ettore RIZZA wrote: > > And, of course, you can also use a SPARQL Query. > > On Fri, 21 Sep 2018 at 21:07,

Re: [Wikidata] Advice for storing retail product data on Wikidata or a self-hosted Wikibase instance

Hey Abe, Maxime, cool that you've been looking into how to use Wikibase / Wikidata for something like a retail products / firearms database. I could definitely understand why you're considering that. I suppose just using the vocabulary and writing your own software is probably the best way to go.

Re: [Wikidata] Indexing all item properties in ElasticSearch

I could definitely see a usecase for 1) and maybe for 2). For example, let's say i remember that one movie that Rutger Hauer played in, just searching for 'movie rutger hauer' gives back nothing: https://www.wikidata.org/w/index.php?search=movie+rutger+hauer While Wikipedia gives back quite a

[Wikidata-bugs] [Maniphest] [Commented On] T198255: Wanted: Wikidata user script to add links using IIIF data

Husky added a comment. @Pigsonthewing sure thing. This should now work.TASK DETAILhttps://phabricator.wikimedia.org/T198255EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: HuskyCc: Husky, Ramsey-WMF, Liuxinyu970226, Jheald, Pigsonthewing, Aklapper, Lahi, Gq86

[Wikidata-bugs] [Maniphest] [Commented On] T198255: Wanted: Wikidata user script to add links using IIIF data

Husky added a comment. Here's something i wrote: https://www.wikidata.org/wiki/User:Husky/ifff-viewer-link.jsTASK DETAILhttps://phabricator.wikimedia.org/T198255EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: HuskyCc: Husky, Ramsey-WMF, Liuxinyu970226, Jheald

[Wikidata-bugs] [Maniphest] [Commented On] T193442: Querying multiple entity labels in one API call

Husky added a comment. @Lea_Lacroix_WMDE what i basically want is an option to use the wbgetentities method with an option to query by label in the same way you can query ids or titles. I was working on matching a set of street names to WD items, i could of course do an individual query for each

[Wikidata-bugs] [Maniphest] [Commented On] T193442: Querying multiple entity labels in one API call

Husky added a comment. @matej_suchanek i've tried that, but unfortunately searching by label using SPARQL is far too slow. Queries time out or take forever.TASK DETAILhttps://phabricator.wikimedia.org/T193442EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences

[Wikidata-bugs] [Maniphest] [Commented On] T193442: Querying multiple entity labels in one API call

Husky added a comment. @matej_suchanek both of these options are not useful, i want to query by label, not by ID.TASK DETAILhttps://phabricator.wikimedia.org/T193442EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: HuskyCc: matej_suchanek, Edgars2007, Husky

[Wikidata-bugs] [Maniphest] [Created] T193442: Querying multiple entity labels in one API call

Husky created this task.Husky added a project: Wikidata.Herald added a subscriber: Aklapper. TASK DESCRIPTIONI developed a tool called Multisearch that allows you to input a list of titles (50 max) with a wiki project and get back a link to the page (if it exists) and the QID of the Wikidata item

Re: [Wikidata] Autocomplete API? [From A visual way to query Wikidata]

It's probably documented somewhere in the API docs, but it's really quite easy, just replace the in this URL to search Wikidata: https://www.wikidata.org/w/api.php?action=wbsearchentities=*=json=en=property= -- Hay On Wed, Jun 21, 2017 at 6:28 PM, Alex Stinson wrote:

Re: [Wikidata] A visual way to query Wikidata

> One suggestion which would be helpful for me is to be able to link to the > Commons Category. Perhaps different options like this could be tick boxes at > the top? Ah, i suppose you want to view more properties of one single item? I think that might work...i'm just not sure if this should be a

Re: [Wikidata] A visual way to query Wikidata

Hey Thad, thanks for the suggestions! Concerning keywords in the description field of properties: i think that is a shortcoming of the current autocomplete API that i'm using, which is the same one Wikidata uses for the searchbox in the top-right corner. Apparently they're not indexing those

[Wikidata] A visual way to query Wikidata

Hey everyone, i've made a tool that allows you to query Wikidata in a visual way without using SPARQL. It's called VizQuery: http://tools.wmflabs.org/hay/vizquery/ The possibilities of using Wikidata to do interesting queries are endless, and the current query service allows for very powerful

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

One other usecase for this would be citation URLs. For example, to get the number of inhabitants of all Dutch municipalities you need a 800-character (1) permalink from the central bureau of statistics. So this change would be very welcome indeed! -- Hay (1):

Re: [Wikidata] Getting the label of a WD property in SPARQL

You need to use the 'wikibase:label' service, see: https://www.mediawiki.org/wiki/Wikidata_query_service/User_Manual#Label_service For example, here's a query with all plays written by the Hungarian playwright Ferenc Molnar with label: select ?item ?itemLabel where { ?item wdt:P50 wd:Q296809 .

Re: [Wikidata] Wikidata Propbrowse

On Mon, Feb 15, 2016 at 10:56 AM, André Costa wrote: > Would it be possible to set the language used to search with? Whilst I most > often use English on Wikidata I'm sure a lot of people don't. Not yet. The query takes quite a while, so it's done in realtime but every 24

Re: [Wikidata] Wikidata Propbrowse

/Sparql > > On Sun, Feb 14, 2016 at 2:44 PM, Hay (Husky) <hus...@gmail.com> wrote: >> >> Hey everyone, >> it seems we're getting new properties every day. Currently there are >> over 2000 properties on Wikidata, and for me personally it's becoming >> a

Re: [Wikidata] Wikidata Propbrowse

On Sun, Feb 14, 2016 at 3:53 PM, Jane Darnell wrote: > Now I suddenly understand why we should have "properties for properties" so > we can categorize these things. It would be nice to have a list of > "authority control" properties and also the number of times a property is

Re: [Wikidata] Wikidata Propbrowse

On Sun, Feb 14, 2016 at 4:40 PM, Markus Kroetzsch wrote: >> I suspect that https://query.wikidata.org can count how many times each >> property is used. > > > Amazingly, you can (I was surprised): > >