-
Notifications
You must be signed in to change notification settings - Fork 15
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
Can't save job listings (without location) since Freebase API is no longer available #57
Comments
Yes, unfortunately the site is in a holding pattern until #38 is resolved. I've done a bit of work moving existing data over to wikidata but there is more work to do, and I'm not 100% sure when I will get to it. Hopefully in the next month. |
edsu
added a commit
that referenced
this issue
Sep 22, 2016
this is step one in moving form freebase to wikidata. I added wikidata_id to the Employer, Location and Subject models. Then I added a migration to lookup the existing entities in Wikidata using Wikidata's SPARQL endpoint. The matching logic thus far is: 1. Look up entity using the Freebase ID 2. Use the name of the entity to derive the Wikipedia URL and look that up 3. To search for the label The next step is to purge entities that don't have Wikidata IDs, and then to create new suggest functionality that uses Wikidata instead of Freebase. refs #38 refs #57
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The autocomplete behavior provided by the Freebase API is no longer working for locations (as well as other tags). Without a location, jobs in the curation queue can't be saved or published.
The text was updated successfully, but these errors were encountered: