search

LD4P / qa_server

A rails engine with questioning authority gem installed to serve as an authority search server with normalized results.
Apache License 2.0
6 stars 3 forks source link

Direct Input of a URI for MeSH does not index the label #325

Open bushmanb opened 4 years ago

bushmanb commented 4 years ago

For tracking purposes, please create a separate issue for each indexing improvement request.

When we try to directly input a MeSH RDF URI because we are not finding the correct descriptor from the QA choices as the subject, the label is not being retrieved and stored. It was our assumption that because MeSH was a cached dataset that the system could retrieve the label which could then be indexed and searched.

elrayle commented 4 years ago

@bushmanb To clarify, you are entering a URI in the field and it is storing the URI as the label of the field?

NancyJean commented 4 years ago

Hi @elrayle. yes, I think we're saying the same thing, but I'm not sure what's happening under the hood and it may be a Sinopia issue rather than a QA issue.

If we manually enter a URI, for a vocab that QA has cached (e.g. MeSH), when we view the data in, e.g., turtle, it displays the URI, not the label. And if we then do a search in Sinopia on the label represented by the URI, the 'resource' we created isn't found. So, yes, it would seem that Sinopia is storing the URI as a label and not taking any action on it.

If a vocab is cached in QA, we thought that entering the URI in Sinopia would return and cache the label. So the label would appear in Sinopia's human readable view of the data (e.g. turtle) while the URI would be stored in the background for machine manipulation. So I think the question is - What is happening in Sinopia when we manually enter a URI rather than a QA option? Is Sinopia querying the QA cache for the label of the manually entered URI or querying the internet or just storing the URI as a label?

If Sinopia is simply storing the manually entered URI and not running any query for and caching the label, then that might affect whether or not we manually enter URIs.

Our use case for this is URIs for MeSH DescriptorQualifierPairs (an pre-existing MeSH URI for subjects that combine MARC subfields a and x). We can't get those DQ pair subject URIs from QA, but we can copy and paste them directly from the MeSH browser.

So, again maybe this is an issue that should be addressed to Sinopia rather than QA?

NancyJean commented 4 years ago

Just checked with Jeremy and this is indeed a Sinopia question. He said Sinopia doesn't currently have functionality to query the internet or QA cache to get and cache in the Sinopia the labels for manually entered URIs.