Because article-level linking is not yet available for some open access databases, Summon is providing links in to non-open access sources while displaying the Open Access Indicator which is confusing for those searching Summon without the credentials for accessing licensed resources. Example: http://tinyurl.com/yd6qc22w Levasseur, T. J. (2012). THE ENVIRONMENT CONTAINS NO "RIGHT" AND "LEFT": NAVIGATING IDEOLOGY, RELIGION, AND VIEWS OF THE ENVIRONMENT IN CONTEMPORARY AMERICAN SOCIETY. Journal for the Study of Religions and Ideologies, 11(33), 62-88.

Either include in the Summon result a link to the open access database where a publication is available open access, or remove the Open Access Indicator, as it is confusing and misleading for the end user.

Aggregators, such as EBSCOhost, post articles on their websites only after the publisher adds the content in a journal issue. However, they do not take this information into account when providing their coverage dates.

Because of this issue, citations in Summon for such "online-first" articles (such as the ones at https://www.tandfonline.com/action/showAxaArticles?journalCode=tsri20) may link to an error message if the institution subscribes to the journal via an aggregator and not the publisher.

Since "online-first" records have a publication (SSID) and a publication date, if you subscribe to the journal and the article publication date falls within your dates of coverage, Summon will surface the record. There is not currently a way to "turn off" single "online-first" articles without also turning off or adjusting your holdings for the whole publication.

It may be a long shot, but I'm wondering if an Ex Libris development team may be able to fix this problem in Summon.

We're delighted that we could integrate SpringShare Chat functionality into our Summon interface. However, we feel it could be improved by delaying the appearance of the chat prompt message for this functionality on screen.

As you can see from the file, a message appears asking users whether they'd like to chat to one of the Library Team - that's great! - but the speed of which it appears is almost instantaneous and often before users have had chance to look at their results.

Is there any way that you could make a fix for Summon to delay this slightly so it doesn't bombard the user straightaway, i.e. have it appear in 1-2 minutes after the search results have loaded?

This would be better for the user experience - they'll really value the message (and many users may want to use it, so that's great UX) but they'll also want to pause and take stock of what they've searched for as well before considering whether to use the chat functionality (and some may not need to use it or wish to use it at all!).

It would be good if we could choose to make either WoS or Scopus citation counts visible in Summon, instead of having to have either both or neither switched on.

Because we no longer subscribe to WoS but do subscribe to Scopus, the only way we could get WoS citation counts removed from the Summon search results was to untrack Web of Science in Intota. We don't like to untrack resources that we've previously subscribed to, because doing so means we can't see any of the historical data attached to Web of Knowledge collection databases. This is just how Intota works, and as there's no ideas exchange category for Intota I can't request a change there. ;)

We would prefer not having had to switch off tracking for WoS in Intota, since we are using it as an ERM and want to have it include historical sub data.

Thanks!

We would like to be able to add, remove or edit query expansion topic matches to improve the topic and subject matches and prevent incorrect query expansion.

Query expansion is supposed to link synonymous subjects and topics, so the user doesn’t have to enter all terms in their search (e.g. ‘heart attack’ and ‘myocardial infarction’). Sometimes the query expansion function gives incorrect or unhelpful topic matches. For example a search for ‘civil litigation’ automatically expands to include ‘jurisprudence’. These are not synonymous terms.

ExLibris tell us that currently it isn’t possible to change or remove specific instances of query expansion, you can only turn the whole feature on or off.