Primo Enhancements - 2nd Round

Fix indexing of words with hyphens (e.g. hand-book, etc.)(4457)

Words / adjacent words with hyphens are not indexed properly. They can be retrieved with the hyphen, or as two separate words, but cannot by retrieved if you omit the hyphen and compress the word/s. This is a general problem, in English and other languages (for example the word "chat-room" is currently indexed as only as "chat-room" and "chat room," but not as "chatroom"). It is especially a problem for Korean name transliterations, as well as older material with different compound word conventions (e.g. hand-book, by-law, year-book). See Use Case field for more examples.  

Ability to search My Favorites / eShelf(6187)

There needs to be a way for a user to find items in a list. One possible solution would be a feature that allows you to quickly search the entire list. This is more important than ever now that the new UI loads only 10 items at a time. DETAILS: When a user has more than 10 items in a list (favorites, loans, historic loans, requests), and they want to find a particular item using Control+F, they will get zero hits if their item is not in the first 10 items in the list (in the new UI), because the system only loads the first 10. They have no way to find the item unless they load the entire list. To load the entire list they either need to load 10 at a time until they have gone through the entire list or export the list and then search it externally, and neither of these are user-friendly workarounds. (See use case as well).  

Create spinner or indicator for GetIt frame to indicate content is loading(6440)

The GetIt frame in Primo often takes 10-15 seconds to load. During that time many patrons believe it isn't working so they close the window. USG would like ExLibris to create a spinner or some sort of visual indication so that patrons know that content is being fetched for the GetIt frame. 

Indicate in UI when query matches doc's indexed full text(6527)

In a Summon discovery interface I came across a useful feature not available in the Primo UI: When performing a search and getting hits not in the metadata but within the indexed full text of the document, this was indicated in the detailed view with the phrase: "Why is this result here? Your query matched the indexed full text of this document." This feature would be useful in Primo as well, and I believe it would work nicely in combination with (but not necessarily depending on) the functionality asked for in request #2958. 

Add 505$t to Primo VE TOC and Title indexes(6552)

The out-of-the-box indexes in Primo VE for Table of Contents and Title do not include enhanced 505 subfield t's (titles). The subfield r's are indexed in the Creator/Author index. We propose adding the $t to the TOC and Title indexes. 

Sort order of libraries/locations(6635)

We are requesting the ability to tailor the sort order of libraries/locations in a more granular fashion by selecting the exact order in which we need these items to appear at both the library and location levels. There are locations such as Africana (protected collection; not for loan) and Law which we want to appear lower on the list than locations Upper Level / Lower Level / Short Loans for example and that we cannot manipulate ourselves and need to. 

Extend customization options for all request forms (6637)

For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users). The current configuration possibilities are much too limited. We would like to have the possibility to: configure mandatory fields if we want the user to specify a field in the form, e.g., to include in the digitisation request form the volume, issue and date of the requested article. to add customizable checkboxes that the user has to tick before proceeding with the request. In the resource sharing form there is a field for Copyright that has this kind of functionality. But we have a need for a more general field, and it should be available in all the forms. add generic text to display general information to the user There are currently differences between Primo and Primo VE on how customizable these forms are; this enhancement would extend the options for both flavors - and they should end up on an equal level. 

Advanced search: add support for "exact only"(6693)

Currently, "is (exact)" is not "exact only". "is (exact) returns results that contain phrases that exactly match the phrases specified in the query." We would like to have a true "is exact" search, where the results inlcude the query term(s) and only the query term(s). 

Ability to dedup or FRBR between local data and CDI data(6702)

For Primo Central Index data collections, the PCI citation often represents a title that we also hold in our local data. The current inability to dedupe or cluster between PCI and local data means that users will always be presented with two hits when they are on the combined/everything scope.  With the new Central Discovery Index (CDI), we would like the ability to configure a deduping or clustering algorithm such that we only present one hit to the user.  (Ideas Exchange https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38763142-ability-to-dedup-or-frbr-between-local-data-and-cd)  

Bad Link Reporter(6703)

This tool would work while librarians are searching Primo. An addon tool for Primo that looks at results when the following condition exists: a link is clicked and user gets an error, (no full text available or other Primo error messages) there would be a popup or message asking “report this bad link?”. You click on the button, it goes away allowing librarian to continue their work but clicking the button reports the permalink, search details and bad link error message including eresource used. We would like to see this option configurable – option 1) only for library staff; option 2) all users. This then gets submitted as a Task that the EResources Librarian can investigate within Alma.   Options:  Instead of a popup, error is reported automatically behind the scenes. Local IT can turn feature off if they are overwhelmed and turn back on later as needed. User could request a “screen capture” that would document error after clicking on link. Then screen capture is automatically linked to the logged error.  Tool keeps track of eResource titles reported.  Give troubleshooter a "quick link" to the problem portfolio in Alma to suppress a portfolio if you have a metadata mismatch or cataloging problem that resulted in bad link or bad result. This would give local library some control over these types of problems.  Currently there is no reporting mechanism for users for broken links found in Primo. Functionality exists in Leganto for users to click 'report broken link' next to each electronic service. This generates an alert which is accessible in Alma from the tasklist. These reports are time and date stamped and include user details and can then be investigated. We would like similar functionality to be developed for Primo which can generate alerts to broken links accessible within Alma.  

Add support for microlanguages ISO 639-3 and language codes recognised by Library of Congress(6710)

Primo currently supports only macrolanguages via ISO 639-2, for hardcoded display of Language in the Language Facet and Language Display fields of the Primo UI. Unfortunately this does not include the wealth of microlanguages used internationally, including Australian indigenous languages known as Austlang, which have been recognised in Library of Congress Language source codes as of October 2018: https://www.loc.gov/marc/relators/tn181026src.html These Austlang language codes, used by many libraries to correctly assign and recognise Australian indigenous languages, are recorded in the 041$a field(s) of the bibliographic record, but do not conform to the three alpha character coding found in ISO639-2 or 639-3. The full list of Austlang codes can be downloaded from : https://data.gov.au/data/dataset/70132e6f-259c-4e0f-9f95-4aed1101c053/resource/e9a9ea06-d821-4b53-a05f-877409a1a19c/download/aiatsisaustlangendpoint_001.csv. Microlanguages, including Austlang (Australian language) codes, should be supported in the out-of-the box language code and mapping tables regardless of Primo deployment models (ie covering both Primo Back Office and Primo VE), and this coding should map to Language facets and Language display without any additional intervention by institutions. These codes would be in addition to the standard language coding already supported. See Idea Exchange entry: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38805802-add-australian-language-codes-to-primo-back-office  

Add Journal Coverage Dates to Brief Results Page (6718)

Add the ability to display the coverage dates found in the Alma portfolio record to the Primo brief results. Upon performing a search for ejournals, our patrons and staff would like to immediately see what our coverage dates are, without clicking into the full details. Library patrons often confuse the publication dates of journals with coverage dates. This leads to unhappy patrons and staff! Many journal titles have multiple portfolios with a range of coverage dates. The ideal scenario would be to have the system calculate total start and end dates for a journal when it has multiple portfolios and show a summary on the brief results page. 

Call number browse: allow limiting by location(6727)

Users should be able to limit by location when browsing by call number. Users want to be able to browse materials in closed stacks or off-site locations by call number, but without seeing materials from other locations, as having all locations together in the browse has too many results for them to be able to browse easily.