[
https://jira.duraspace.org/browse/DS-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23341#comment-23341
]
Mark Diggory commented on DS-1080:
----------------------------------
I agree with adding this support, we should actually consider a more general
solution where the xmlui xslt layer has access to the results of the solr
search more directly.
We currently have an approach that is restrictive to the xslt their getting at
the whole results of the solr search, this is because we married the results
and the configuration of the view for discovery into its own domain model. But
also we suffer from the case that the Wing framework limits what can be put
into a reference object.
We will need to come up with a place within the DRI where we would encode the
solr search results. My current recommendation is that we return to the
approach we took in one of the original prototypes. We would encode the solrj
results into DRI elements and render them as a dri list, dropping the use of
DRI references in favor of extending the DRI wing to support adding the details
of the ReferenceSet/reference groups as attributes of DRI lists rather than a
reference "element", this would allow us to transport all the solr search
result characterists as part of the DRI and write xslt to render extended
capabilities like spellcheck, hit highlighting and relevancy directly when
rendering the search results.
This doesn't mean that we wouldn't allow use of the reference / mets for
getting into the item metadata, but that we will invert the processing so that
if METS content is only gotten when required in rendering the search results.
its a lookup into the mets document from the context of the dri search results
rather than handing the entire context of xslt processing over into the mets
document instance.
Anyhow, I agree highly with the need to support this capability and anticipate
we will add it to a future release.
> Search results preview
> ----------------------
>
> Key: DS-1080
> URL: https://jira.duraspace.org/browse/DS-1080
> Project: DSpace
> Issue Type: New Feature
> Components: Discovery, XMLUI
> Reporter: Howard Shand
> Assignee: Mark Diggory
> Priority: Major
> Attachments: example.jpg
>
>
> Show a preview of search results.
> When search results are based on full text search, show the keywords in their
> context (with some highlighting) similar to the functionality of most search
> engines.
> Example of the system we were previously using is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
