-
Notifications
You must be signed in to change notification settings - Fork 8
Implement OpenRefine reconciliation API #168
Comments
Thanks for the input Tom, that sounds lika a very interesting idea. By 'implemented natively', do you mean native to api.lobid.org, i.e. building it as part of the Lobid API itself, instead of as a separate service (and therefore making it easy to find from api.lobid.org)? From the documentation it sounds like it's all about HTTP and JSON, so I assume you don't mean native to OpenRefine in any way, right? |
Yes, I mean having a native reconcile endpoint eg. api.lobid.org/reconcile to complement the /search endpoint. For example, OpenCorporates version looks like this: http://api.opencorporates.com/documentation/Google-Refine-Reconciliation-API The advantage is that people can load a CSV into OpenRefine and match it against your data without having to break out their favorite programming language. |
FYI: I'm very interested in such a reconciliation service for OpenRefine, too. |
Sorry for pushing: Is there any chance that this will come? |
@hauschke We're currently all quite busy with a short running project with a tight deadline. I'll try to look into this by the end of March. I can't make any promise about how fast we'll have something running though. |
Two Marches later: Is there any progress on this? Edit (July, 2nd): As it is possible to get data via JSON, it's not critical. |
We've started working on an OpenRefine reconciliation service for lobid-organisations. See hbz/lobid-organisations#55 (comment) for details. |
Implemented for lobid-organisations. No request yet to add this for lobid-resources. Closing. |
It'd be useful to have a reconciliation service which could be used directly with OpenRefine. Such as service could be built as a broker to the existing API, but it'd be a) easier to find and b) more powerful if implemented natively.
Ideally a reconciliation service would taken into account more than just a name match. Having the ability to specify things like nationality, birth, & death date in the scoring would provide for better quality matches and less human review.
Documentation of the API is available here: https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API and there are some simple example implementations on Github too, such as https://github.com/OpenRefine/reconciliation_service_skeleton
The text was updated successfully, but these errors were encountered: