Home » OneSearch (Page 6)
Category Archives: OneSearch
Why Does OneSearch Say We Have the Electronic Book?
We’re finding that the Merck Manual is in our results as an e-resource but we only have it in print. Why does this happen? OneSearch interprets cataloging quite literally. In this case, the MARC record contains this 856 field (full record): 85641 $uhttp://www.merck.com/pubs/mmanual%5Fhome2/ The second indicator has a mission-critical role (MARC 856 field @ LOC) # […]
New in OneSearch: Enriched Browse
OneSearch’s Browse now has a new feature: “See” references! When browsing by either Author or Subject, the results now link to the preferred term from the non-preferred term. For example, when browsing the author “shakespeare, g,” OneSearch shows that “Shakespeare, William, 1564-1616” is the preferred form to “Guglielmo” and provides a link to that preferred author: […]
“Off campus?” prompt now appears only off-campus
Tired of seeing the “Off campus?” prompt in OneSearch while you’re on campus? Then do we have good news for you! Users will no longer be prompted to sign in if their IP address is within the campus’s IP space and they’re viewing their local college’s OneSearch instance. (That is, if a student is at […]
Primo customizations worldwide
There are over 2,100 Primo customers worldwide. Want to know how some of them have customized their discovery tool? Check out the list of Primo sites on the Ex Libris Users of North America (ELUNA) website! Some notable customers include: Harvard University http://library.harvard.edu/ The Royal Library (Denmark) http://rex.kb.dk/ Tulane University http://library.tulane.edu/ If you like something […]
New in OneSearch: Journal Issue Filtering
Problem Years of journal issues can be impossible to wade through when trying to locate specific issues. Solution Filters on Location, Year, and Volume. This tool was already available in the CUNY Catalog and has now been added to OneSearch, too. Now, when there are sufficient issues to make filtering useful, filters will be offered above the issue […]
