Page MenuHomePhabricator

Wikidata entity selector for 3rd party usage
Open, MediumPublic

Description

Wikidata concepts are very useful for tagging content on 3rd party websites and other cases where a specific concept needs to be chosen. For this 3rd party developers shouldn't need to develop their own entity selector. We should provide something similar to what Freebase offered with Freebase Suggest.

Event Timeline

Lydia_Pintscher raised the priority of this task from to Medium.
Lydia_Pintscher updated the task description. (Show Details)
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 16 2015, 2:02 PM
edsu added a subscriber: edsu.EditedMay 17 2015, 11:28 AM

As a current user of Freebase Suggest, which is going away apparently on June 30th, it would be super to have a Wikidata based alternative. I suspect (but do not know) that there are other Freebase Suggest users who will need to migrate to something, and having a path to Wikidata would be good for Wikidata entities being used outside of the Wikipedia ecosystem.

I see that the searchbox at www.wikidata.org is using this API call?

https://www.wikidata.org/w/api.php?action=wbsearchentities&search=ch&format=json&language=en&type=item&continue=0&callback=foo

To be able to use that API call on another website I guess there would need to be a .js file that could be loaded from www.wikidata.org (same origin policy). Or perhaps there is a way to get it to work with the JSON-P callback parameter, or if CORS headers are set up appropriately from the wikidata API call?

Jonas renamed this task from separate out entity selector for 3rd party usage to [Story] separate out entity selector for 3rd party usage.Aug 15 2015, 12:45 PM
Jonas set Security to None.
Astinson added a comment.EditedAug 31 2017, 5:06 PM

An additional story: In an institutional website, a cataloger wants to create a metadata tag, that includes both a plain text and a URI based reference for what they are describing -- for fields created by the institutional website using some metadata standard. As an institutional website developer, I want to provide a suggestion box for that field, so that the cateloger uses our controlled vocabulary (based on Wikidata), instead of having to either a) copy and paste qids into the field or b) do the matching in a seperate ecosystem (say Google Spreadsheets or Open Refine). The output of the tool needs a plain-text label for human readable use of the catelogue/collection software, and the uri in a format appropriate for linked-open data schamas.

Open questions:

*Could we create a "model widget" that could be used by developers on common institutional platforms (Drupal, Dspace, Koah etc) , that provides access to an auto-fill tool, that is akin to what folks get when adding a property and value on Wikidata?
*What kinds of background/context would be needed to successfully develop this?

Abbe98 added a subscriber: Abbe98.Sep 16 2017, 6:00 PM
SandraF_WMF moved this task from Backlog to Wikidata + GLAM Open on the GLAM-Tech board.
Lydia_Pintscher renamed this task from [Story] separate out entity selector for 3rd party usage to [Story] Wikidata entity selector for 3rd party usage.Apr 7 2018, 11:23 AM
Lydia_Pintscher updated the task description. (Show Details)
Lydia_Pintscher renamed this task from [Story] Wikidata entity selector for 3rd party usage to Wikidata entity selector for 3rd party usage.Apr 7 2018, 11:29 AM
Cparle added a subscriber: Cparle.May 3 2018, 3:56 PM
Susannaanas added a subscriber: Susannaanas.