Records with NO ResourceProxies

[matej.durco@oeaw.ac.at]

There are numerous records without any resource proxy.

The VLO query for that:
​https://vlo.clarin.eu/search?q=resources:0+-_searchPageRef:*+-_hasPartCount:*+-_contentSearchRef:* yields around 20.000 records (|21171| as of 2018-02-20)

out of these from CLARIN centres:
​https://vlo.clarin.eu/search?q=resources:0+-_searchPageRef:*+-_hasPartCount:*+-_contentSearchRef:*&fqType=dataProvider:or&fq=dataProvider:CLARIN+Centres (|8200| as of 2018-02-20)

Following is the list of offending collections:
​http://alpha-vlo.clarin.eu/solr/vlo-index/select?facet.field=collection&facet=on&q=resources:0%20-_searchPageRef:*%20-_hasPartCount:*%20-_contentSearchRef:*&rows=0

On the one hand, we agree that records without resourceproxies have little value for the user, but there seems to have been a decision (and a good reason) to still keep those in.

This could be resolved (or at least made explicit to the users) by a dedicated availability facet.

For now we at least want to keep track of this phenomenon, here.

[Twan Goosen]

See ​https://github.com/clarin-eric/VLO/issues/134

[Twan Goosen]

The situation is actually better in the current develpoment version. The correct query to verify is the following:

resources:0 -_searchPageRef:* -_hasPartCount:* -_contentSearchRef:* -_landingPageRef:*

(notice that landing page als have to be excluded)

Compare:

• ​production |16002|
• ​alpha |365|

The remaining records actually do have resource proxies, but these are (at least according to my sample) all cases of metadata resource proxies that do not resolve to a record included in the VLO. Therefore effectively these records have no resources, landing page, search page or service references, content search reference, or 'parts'.

[Twan Goosen]

The remaining cases (which are no longer showing up in the VLO as of version 4.4) should already get identified by the curation module, and detected as part of the resource proxy checking - see #1052.