tfmorris suggest it could be an upgrade issue and this service should not be used.
The reconciliation services I see are:
11:36:13.186 [ refine] POST /command/core/guess-types-of-column (9400ms)
11:36:16.806 [ command] Failed to guess cell types for load
There is a $265 open bounty on this issue. Add to the bounty at Bountysource.
The standard style of Freebase reconciliation is still supported, but I'm guessing that we're not correctly upgrading existing installations. This was an upgrade from Google Refine 2.5, correct?
The URL listed:
is the old reconciliation service. One clue is the "Could not fetch URL: http://api.freebase.com/api/service/search?read=15000" error message. That's the previous API endpoint which Google has decommissioned.
The new reconciliation services lives at
As a workaround, you should be able to add it by hand (Add Standard Service button at bottom left of reconciliation dialog).
I'll have a look at what needs to be done to make the upgrade smoother.
It's not an upgrade actually, I am using the last version from github.
I was able to configure the new service by hands, thanks!
@tfmorris Fwiw, I installed 2.5 on a mac last night and then when I installed 2.6-beta.1 I saw this issue. The suggested workaround works. Thanks!
@cldwalker Thanks for the confirmation. We'll have it fixed before the next kit goes out.
I just downloaded the trunk (and cleaned the settings ) and I still have this problem using freebase reconciliation.
Creating a new reconciliation service using the new url works.
This the error:
<h1>Error in <span class="script">//standard-reconcile.freebaseapps.com./reconcile</span></h1>
<p class="msg">JS exception: acre.errors.URLError: urlfetch failed: 410</p>
We just need to add support for the new Freebase /reconcile service on googleapis
And ensure that a OpenRefine user has a dialog box where they can input their API key.
There are a couple of different problems describe in this thread. The most recent problem is that the entire freebaseapps.com domain has been retired, so anything that lives on it, including our new Freebase reconciliation service, is gone.
@thadguidry The new reconciliation APIs have been supported since they were introduced. Unfortunately they were proxied through a service which has been shut down by Google. We can either:: a) host the service somewhere else or b) special case Freebase support differently from all the other reconciliation services and self-host it in the Refine server.
b) self host in Refine. I already spoke with David H. today about that actually and he also thought it was a good idea.
If the reconciliation service is hosted on the machine running refine, what are the impact on the local resource comsumption (RAM and processor). Refine is already demanding on local resource for large project, should we worry about adding an other local service?
Martin, The design should support the reconciliation service to be OFF by default, and enabled as an OpenRefine preference.
Eh, I was planning a whole project based on this feature and it broke... Some sort of alternative is to use Fetching URLs From Web Services but that can be slow, limited (single query request) and it creates another column which I will have to rename after deleting previous one? Do you have any other temporary better idea?
Do you have an advice on how to implement this?
In order to start I'd like to know where is the code of the existing wrapper.
I have updated the bounty / issue to reflect the new needs for Wikidata Reconciliation. (Given that Freebase is going away and will be absorbed into Wikidata this spring)
The starting point for those interested looks like this:
Help for the Wikidata API is here: https://www.wikidata.org/w/api.php
I did implement one a while ago, partially. Will that do?
Its a bit more than just your server side on Wikidata :) changes also need to be done on our client side in OpenRefine as well. Essentially, the Freebase Standard Reconcile as a default needs to be replaced. This requires working through and cleaning up most of the Java, JS, HTML, and JSON files here: https://github.com/OpenRefine/OpenRefine/search?utf8=%E2%9C%93&q=reconciliation+OR+reconcile+OR+recon&type=Code
The bounty gets awarded when both sides are done. The bounty can be split between developers if they wish, for instance, if you want to have someone do the client side improvements in our code, while you take credit and a partial bounty for the server side. Up to those involved, we don't care as long as it gets done properly and tests complete. Good luck, get others involved, or finish it all yourself :)
Also @magnusmanske when OpenRefine performs the guess-types-of-columns command there's sometimes failures against the Wikidata reconcile. I know that Wikidata doesn't really have Types, but instead of displaying Q numbers, our users are looking to see name values, like "automobile", "animal", etc... not Q1420 and Q729, etc.