We have resolved the issue on our end by reverting to the old behavior of showing the metadata's abstract (if available) with a full-text match.
For our site if the abstract is restricted, the text of the dc.description.abstract field just says a note about being restricted -- effectively hiding anything that might otherwise be revealed by just showing that metadata field. The result actually ended up looking more attractive by always showing an abstract (if present in the metadata), hiding restricted content, avoiding showing the encoding characters at the beginning of the fulltext index on some results <https://jira.duraspace.org/projects/DS/issues/DS-3090>, and still showing Hit Highlighting if the search term was in the title or certain other item metadata. My technical challenges encountered, thoughts, and code are listed here: http://stackoverflow.com/a/36486231/469643 -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
