Failing Connection Test: MESH_NLM_NEW_LD4L_CACHE/subject q=Spain

[elrayle]

Browser Access for Test:

https://lookup-int.ld4l.org/authorities/search/linked_data/mesh_nlm_new_ld4l_cache/subject?q=Spain&maxRecords=4&context=true

[]

The old indexing approach returns 1 result: https://lookup-int.ld4l.org/authorities/search/linked_data/mesh_nlm_ld4l_cache/subject?q=Spain&maxRecords=4&context=true

Monitor Status results in UI:

CURL access directly to wintermute

$ curl -L -D - -H 'Accept: application/n-triples' 'http://wintermute.slis.uiowa.edu:8081/ld4l_services/mesh_batch.jsp?query=Spain&maxRecords=4&startRecord=1&entity=Subject&lang=en'
HTTP/1.1 200 
Set-Cookie: JSESSIONID=F66ED6680E253D2984A95E1156E106CA;path=/ld4l_services;HttpOnly
Content-Type: application/n-triples;charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 10 Dec 2020 18:34:15 GMT

<http://ld4l.org/ld4l_services/cache> <http://vivoweb.org/ontology/core#count> "0" .

[elrayle]

ACTION: @eichmann will explore why this query returns 0 results. We confirmed that Spain should return results in the subject subauth.

[elrayle]

This is confirmed to work on integration and will be in the next production release.

[elrayle]

I cannot confirm a fix for this. I believe I accidentally tested against production instead of the test service for the new indexing.