Our approach until now has been to use mostly raw Solr search results to power the front-end. The advantages being that it's fast and conceptually quite simple.
There are a few disadvantages:
Using Solr to explore relationships: When we browse a collection, we are using RELS-EXT relationships as coded in Solr. This is okay most of the time, but perhaps not always optimal?
There is no connection to more thorough item metadata for items in search result.
One possible, easy to implement solution:
After solr search results, of any kind, interweave URLs for an single item response into the search results. Result would be something like...
Our approach until now has been to use mostly raw Solr search results to power the front-end. The advantages being that it's fast and conceptually quite simple.
There are a few disadvantages:
RELS-EXT
relationships as coded in Solr. This is okay most of the time, but perhaps not always optimal?item
metadata for items in search result.One possible, easy to implement solution:
After solr search results, of any kind, interweave URLs for an single
item
response into the search results. Result would be something like...