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

OpenRefine reconciliation endpoint does not work in testbench #425

Open
acka47 opened this issue Oct 1, 2019 · 3 comments
Open

OpenRefine reconciliation endpoint does not work in testbench #425

acka47 opened this issue Oct 1, 2019 · 3 comments
Assignees

Comments

@acka47
Copy link
Contributor

acka47 commented Oct 1, 2019

Although everything works locally when following the instructions in #55 (comment), I don't get the endpoint to run properly in the testbench.

When I input http://lobid.org/organisations/reconcile (without ssl) as endpoint, I get:

The endpoint must return a JSONP document describing the service.

When inputing https://lobid.org/organisations/reconcile, I can test reconciliation queries (e.g. "Stadtbibliothek Kempten ") but will get:

Error: Cannot read property 'result' of undefined

@wetneb
Copy link

wetneb commented Dec 2, 2019

Have you disabled mixed content blocking in your browser? By default, calls to HTTP services are blocked by your browser as the testbench is served over HTTPS. It's annoying. Turning off HTTPS on GitHub pages does not seem possible unless we register our own domain name (we could probably get a subdomain of openrefine.org for that though, but I would prefer to keep the reconciliation CG and the OpenRefine project separate in theory…)

@acka47
Copy link
Contributor Author

acka47 commented Dec 3, 2020

The JSONP problem is fixed – probably as we added SSL support in the meantime. However, I now getthe following error message:

Validation errors for service manifest
should have required property 'versions'
.defaultTypes[0] should be object

@wetneb
Copy link

wetneb commented Dec 3, 2020

Those are obtained by validating your service manifest against the JSON schema in the specs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants