Closed jschnasse closed 8 years ago
Thx, this is a nice low hanging fruit, yummy :) . Enjoy e.g. http://lobid.org/resources/HT013304490.
But:
items
endpoint - you provided a rewrite that would e.g. work with http://gaia.hbz-nrw.de:9200/resources/HT012926727:DE-38:28A2398 (which is not working, opened the issue #293), but it should better be http://gaia.hbz-nrw.de:9200/items/HT012926727:DE-38:28A2398.@jschnasse besides the two issues that have arised from this ticket, are you comfortable with the solution?
The rewrite from http://lobid.org/resources/HT013304490 seems to got to:
http://gaia.hbz-nrw.de:9200/resources/resource/HT013304490
instead of:
http://gaia.hbz-nrw.de:9200/resources/resource/HT013304490/_source
Fixed. Using
RewriteRule ^/resources/(.*) http://gaia.hbz-nrw.de:9200/resources/_all/$1/_source [P]
+1
Deployed to production, closing.
Yesterday I noticed that API 2.0 will coin totally new URIs using http://lobid.org/resources instead of http://lobid.org/resource . What I like to suggest is to make the new URIs work for requests with
GET accept: application/json
this can be done immediately with a simple apache rewrite something like/resources/$1 http://gaia.hbz-nrw.de:9200/resources/_all/$1/_source
should do the trick. The advantage would be (hopefully), that sameAs links (e.g. ZDB vs. HT) in the current 2.0 index can be used directly without any postprocessing. Also it would provide the new index as linked data.