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
Index full place name from geonames #1065
Comments
Was this closed in #1956? |
This issue is still present in Hyrax 3.0.2. When I add location metadata via geonames, only the first part of the name appears. Example: https://nurax-dev.curationexperts.com/concern/generic_works/6395w720f?locale=en |
This work was in the ❯ git branch --contains 79a19df136bd85ce2b0f283718fba5bf79c6303d
error: no such commit 79a19df136bd85ce2b0f283718fba5bf79c6303d So, yes, the PR resolved it, but we never got this into |
I'm reviewing the current implementation, and it varies significantly from the non-merged commit (aka 79a19df). I am updating the existing spec to highlight that the When I look at the https://www.geonames.org/5037649/about.rdf URL, there's no state code, just country code. Which we know to be inadequate. However, changes introduced in #1956 are breaking changes (updating the generator and removing constants), so I can't use them directly. I'll be bringing this up during stand-up. For now, I'm going to work on getting a local test suite up and running so I can verify what I already have. |
As I'm working through #1065, I needed to understand the default behavior. I also wanted to look and see if there were more attributes on the RDF document that I could add to the label. I'm also considering that #1956 required a change in implementation; moving away from RDF and towards the JSON response document. At present, I'm uncertain on the best approach to proceed with resolving issue #1065. I'll be bringing this up in the hyrax-wg channel and during stand up.
As I'm working through #1065, I needed to understand the default behavior. I also wanted to look and see if there were more attributes on the RDF document that I could add to the label. I'm also considering that #1956 required a change in implementation; moving away from RDF and towards the JSON response document. At present, I'm uncertain on the best approach to proceed with resolving issue #1065. I'll be bringing this up in the hyrax-wg channel and during stand up.
When I choose "Sheffield, South Yorkshire, United Kingdom" and it's indexed as 'Sheffield' ... and ditto for "Sheffield, Tasmania, Australia"
The text was updated successfully, but these errors were encountered: