-
Notifications
You must be signed in to change notification settings - Fork 0
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
Values of hasFeatureType use wrong place type URIs (extra /plone in URI path) #518
Comments
The problem is currently only manifest in the bulk download in TTL format, generated weekly on Sundays and obtained via https://atlantides.org/downloads/pleiades/rdf/:
In evaluating any fix, we should check for these problems not only in the bulk TTL format, but also in both of the individual place-level RDF serializations where the problem is not currently found:
|
@paregorios I regenerated the full archive on staging the way it's generated "in the wild" (via cron), and I think it's looking good. I have not tested the per-Place rdf download, but I didn't find any common code paths, so I think that will be OK (but please test!) |
@jessesnyder can you double-check that the gzipped tar file you attached above is the result of the latest staging run with modified code? I'm still seeing
and so on across all |
@paregorios The archive does indeed not contain the files I expected it to contain. Not sure what happened. Running the cron task again now. |
OK @paregorios, take 2: |
@jessesnyder that's got it! And the individual serializations are still fine too. Please merge, wrap, ship, refrigerate, and deploy to production. |
Deployed 🚀 |
This is fixed in the weekly export on 10/13. Closing as resolved. |
In the RDF datasets, values of
pleiades:hasFeatureType
have URIs with an extra/plone
at the start of the path, like:They should be like:
This currently breaks SPARQL joins between places and their type concepts.
The text was updated successfully, but these errors were encountered: