HandleResolver does not work on catalog.clarin.eu server

[patdui]

The handleResolver api is used to get the name of a resource based on the handle, see ResourceLinkPanel?.java. This does not work on the catalog.clarin.eu server. This server is in the Demilitarized zone and is thus slighlty different then our test server. What happens is the HandleResolver? tries to get the ip adres of our local handle server this server has two ip adresses an external and an intranet one. One of them doesn't work on from the catalog server. Tobias also knows a bit more about this.

Eric also had some contact with the handle api guys and told us to use: HandleResolver?.sendRequestToSite()
Which is not as trivial as it sounds but it could be an option. Another options is to just to our own http requests and get the data from that.
NOTE that the vlo has to work with handles in general and not only with our own handles.

[dietuyt]

This needs more attention. Handles are an important pillar of our infrastructure and we should be able to give a good support in our software. Tibor Kalman (tibor.kalman at gwdg.de) can help with API problems.

[dietuyt]

bump - Herman, as you know how to contact the MPI sysadmins, can you have a closer look and talk to them to get this fixed? thanks!

[dietuyt]

This has been (partially) solved in release 2.10, but still not all handles are resolved, see eg:

​http://catalog.clarin.eu:8081/vlo/?wicket:bookmarkablePage=:eu.clarin.cmdi.vlo.pages.ShowResultPage&fq=collection:MPI+CGN&docId=test-hdl:1839/00-0000-0000-0001-53A7-1

[dietuyt]

The current workaround (to use the hdl.handle.net HTTP proxy instead) seems to work reasonably well, lowering priority. Still it is faster to use the handle API directly.

[dietuyt]

Maybe look at the experimental REST API: ​http://www.handle.net/overviews/rest-api.html

[Twan Goosen]

3.0 is using the REST API and it works quite well. Using the JAVA library might be slightly preferable, see #550.