Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement OpenRefine reconciliation API #168

Closed
tfmorris opened this Issue Oct 1, 2013 · 8 comments

Comments

Projects
None yet
4 participants
@tfmorris
Copy link

commented Oct 1, 2013

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

@fsteeg

This comment has been minimized.

Copy link
Member

commented Oct 2, 2013

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?

@tfmorris

This comment has been minimized.

Copy link
Author

commented Oct 4, 2013

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.

@hauschke

This comment has been minimized.

Copy link

commented Jan 20, 2014

FYI: I'm very interested in such a reconciliation service for OpenRefine, too.

@hauschke

This comment has been minimized.

Copy link

commented Feb 20, 2014

Sorry for pushing: Is there any chance that this will come?

@fsteeg

This comment has been minimized.

Copy link
Member

commented Feb 21, 2014

@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.

@fsteeg fsteeg removed the 0 - Backlog label Jul 24, 2014

@hauschke

This comment has been minimized.

Copy link

commented Jul 1, 2015

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.

@fsteeg

This comment has been minimized.

Copy link
Member

commented Aug 11, 2015

We've started working on an OpenRefine reconciliation service for lobid-organisations.

See hbz/lobid-organisations#55 (comment) for details.

@acka47

This comment has been minimized.

Copy link
Contributor

commented Jul 12, 2017

Implemented for lobid-organisations. No request yet to add this for lobid-resources. Closing.

@acka47 acka47 closed this Jul 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.