First round Primo Enhancements 21-22
ID | Title | Model | Description | Use Cases | Justification |
|---|---|---|---|---|---|
4460 | Browses: add See Also and Usage info from authority headings (VE/BO) | (VE/BO) | Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used. | Example headings and See Also and Usage info that does NOT currently display in Primo: |
|
6187 | Ability to search My Favorites (VE/BO) | (VE/BO) | We need a way for a user to search their list of Favorites. PROBLEM: When a user has many Favorites and they need to find a single one they have in mind, there is no way to search their list. For example, a user may need to export one of their Favorites to EndNote. If they have a list of 150 Favorites, there is no way to do keyword searching to find that Favorite. Some users try to use Control+F to find the Favorite, but because the page loads 10 at a time, it will not find the favorite that is beyond the tenth in the list. | A user has 200 saved favorites. They remember they saved an item in the past with the word "dogs" in the title but they don't remember anything else about it. They go to their Favorites and use Control+F to search "dogs" and get zero hits and think the system is not working, or their memory is failing, when in fact the title is in their list but is number #197. | Users need to find items in their Favorite list to perform certain actions, such as send to EndNote, or navigate to Get It so they can place a request. |
6196 | Consistent order of multi-lingual values in author/topic facets (VE/BO) | (VE/BO) | Currently, in author/topic facets sorted "by size", same values in different languages are displayed in random order. We suggest configuring a consistent language order so that multi-lingual values of the same authority will be clustered together and be displayed by the language-determined order. Containing the multi-lingual values, the cluster will be considered as one value to be sorted in the facet.
|
|
|
6557 | Hide completed purchase requests from the Primo MyAccount (VE/BO) | (VE/BO) | Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount. For each request type libraries should be able to configure which display to users by status. | Patrons who regularly submit purchase requests can be overloaded with dozens of approved or rejected purchase requests in their MyAccount (screenshot attached). | In My Account, completed/cancelled/inactive requests are not displayed to users. However, completed and rejected purchase requests are displayed. This is inconsistent and confusing for users. This enhancement would allow libraries to choose to display or to hide completed/cancelled/rejected/inactive requests for each request type. |
6729 | Prevent Autocomplete suggestions from non-activated sources in CDI (VE/BO) | (VE/BO) | In Primo you can activate autocomplete to get suggestions for search queries based on what the end user begins to type in the search box, which is a useful feature for the end user. However, the suggestions from the central index are currently from the entire index and not only the sources the institution has activated. This means that the end user will get suggestions that gives zero results. We would like there to be a configuration option so that the site can choose for the suggestions to be based only on activated sources in CDI for the given institution. Also added to Idea Exchange: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/39435676-limit-autocomplete-suggestions-from-pci-cdi-to-act |
|
|
6783 | Facilitate entry of data into the resource sharing form from an external source (VE/BO) | (VE/BO) | Recent user experience testing for our resource sharing service indicated users would like a way to easily paste in data from other websites into the resource sharing form. For example, they would like to harvest the data easily from Google Scholar or another database and enter this into the form without manually copying and pasting each piece of data from one website into the webform. One way this could be accomplished is using a browser extension similar to Leganto's Cite It. When they find a resource they would like to request, this browser extension could harvest the required data. The user could then open the resource sharing form and paste all the data at once from the browser extension into the form. |
|
|
7186 | Collection Discovery usage in Primo Analytics (VE/BO) | (VE/BO) | Currently, Analytics possibilities for "Collection Discovery" are rather limited. With action "Display a Collection", you can for example see how many times your collections (all together) have been displayed, added to favorites... in a period of time, but you cannot see which collections are the most and the less successful, what materials should maybe be more promoted, which collection should maybe be removed because its content is maybe of too little interest, which collections are added to favorites, etc. Therefore, we would like Collection IDs and Collection Names to be transferred to Primo Analytics. Additionally, if this could also be done for collection items (MMS ID and Title), this would be very useful too! |
|
|
7398 | Add the ability for Primo users to perform a DOI or PMID lookup to pre-populate the blank Alma Resource Sharing form (VE/BO) | (BO) | Primo offers a variety of means to locate records and access services to place requests. Users may sometimes choose a pathway which is not ideal, but which feels natural and intuitive to what they are hoping to achieve. As an example, a user may go directly to the blank Resource Sharing form, which requires manually typing or copying in information, even when there may be a record for the resource in expanded search. We wish to support our users with streamlined steps in whichever pathway they choose to take to our services. It would therefore be beneficial to be able to do a DOI or PMID (PubMed ID) lookup which would automatically prepopulate the form, saving the user much time in this pathway. Other vendors offer this capability, such as Research Solutions in their Reprints Desk software (https://www.researchsolutions.com/ ). See Requests Desk screen shot attached. Suggested DOI/PMID lookup pathway: 1. Position a DOI/PMID field at the top of the form, 2. User enters DOI / PMID and clicks "Get citation" button, 3. System responds with a match / "Do you wish to prepopulate the form?" or "no match" message, 4. If a match is found user responds with Yes, 5. Form is prepopulated for the user, who can then submit | As a University of New South Wales member of staff / post-graduate student I want to be able to enter a DOI/PubMed ID to prepopulate required fields when submitting an interlibrary loan so that I can more efficiently submit requests without having to manually copy bibliographic information and reduce errors. |
|
7399 | Customisation of resource sharing status messages in the Primo My Library Requests tab (VE/BO) | (VE/BO) | We request the option to customize patron-facing status messages during the interlibrary loan process.
It must be possible to: | As a University member of staff / post-graduate student, I want to clearly understand the current status of my interlibrary loan request so that I can track the progress of my item myself and know when it is ready for pickup / delivery. |
|
7400 | Add "Request another item", "Check current requests" and "Close" options to the "Request placed" page that displays after a Primo Resource Sharing request has been placed (VE/BO) | (VE/BO) | See the current Request placed page display attached. | As a University member of staff / post-graduate student, I want to be able to seamlessly create another request by not having to close and then reopen the request window, plus have the option to return to Primo so I can continue my other activities. This would make the process of submitting multiple requests more efficient |
|
7401 | Provide the ability to view historic requests including Alma Resource Sharing requests (VE/BO) | (VE/BO) | Currently, patrons have queried their request history with staff resulting in extra work for staff and delays for information for patrons as it involves either looking in the resource sharing requests system (resource sharing requests) or building analytics reports (patron physical items requests) for users to extract this information.
| As a University s student / member of staff, I want to be able to view my past requests, so that I have a central record of what I've requested and received and so that copyright is less likely to be infringed. |
|
7516 | User authentication -- adding labels for error messages (VE/BO) | (VE/BO) | Trying to login to Primo as a user with an expiration date that has passed, you get the error message attached. I.e. you are informed that there is an invalid UserID or password. | Case: 00920094 |
|
7599 | New records facet according to Inventory date (VE/BO) | (VE/BO) | The facet for New records (last month, last week) retrieves records according to the bibliographic record creation date. |
| In some institutions is it takes an average of one month from when the record is created until it is available to the user, therefore, the new records that are available in the last week for the user appear under the last month facet or even, sometimes, in the last three months. |
7600 | Include all subject keywords and summary/abstract fields when exporting to Mendeley (VE/BO) | (VE/BO) | When we export records from Primo to Mendeley, all the information in the subject keywords and summary/abstract fields (including MARC 520 and from CDI) are not exported. Ex Libris has indicated that this is an enhancement. We request that all information in these fields be included in the export to Mendeley. |
|
|
7602 | Add configuration option to enable and disable the display of snippets (VE) | (VE) | Brief results often show a quote/snippet for an article (see attached screenshot). In Primo VE it is currently not possible to enable/disable this. We would like to see this configuration option. All the other fields are customizable, why not this one? For Primo BO there is an option to disable this in the view wizard (Show Snippets; Snippet Display Preferences), but Primo VE has no such option. The Primo VE configuration options should match those available in Primo BO. It is possible to hide the snippets with CSS, but this is not a viable solution for all institutions, requiring custom code that may not be locally supportable. |
|
|
7604 | Make citation trail available in the Primo pinned/saved records list and in full records accessed from the saved records list (VE/BO) | (VE/BO) | Please make the citations trail available in the saved records list and in full records accessed from the saved records list. | Currently when a user pins or saves an article that has a citation trail, the citation trail does not display in the saved/pinned titles list. When the user accesses the full record from their saved records list the citations trail does not display in the full record either. | This is problematic for researchers etc. who may save a number of records without realizing they will lose access to the citation trail. |
7606 | The Primo VE Availability indicator for consortia should match what was in Primo Back Office (VE) | (VE) | We have had several users report in a week that they are confused by the lack of accuracy in the availability indicator in Primo VE. | For example Milwaukee noticed that this item shows that it is available in another institution- https://wisconsin-uwm.primo.exlibrisgroup.com/permalink/01UWI_ML/cc3uhc/alma9912304483902121 | We would want VE to be accurate so users do not think that another institution has an item, when it is really checked out. |
7607 | Sort purchase requests in user account by newest (VE/BO) | (VE/BO) | It would be really helpful if user were able to sort their purchase requests in Primo by purchase-request creation date newest. Now Primo shows their purchase requests sorted by oldest, normally the user wants to see the follow up of the most recent. |
|
|
7673 | Allow CDI records and external resources to be added to Alma collections for Primo Collection Discovery (VE/BO) | (VE/BO) | Sometimes we have a title that we'd love to include in these lists, but then find that a record exists only in CDI but not Alma. There may also be single external resources (websites, etc.) that we'd also like to highlight. Currently there is no way to add CDI records nor single external resources to these collections. |
|
|
7688 | Expand-collapse functionality in the Full Display's Details section (VE/BO) | (VE/BO) | Bibliographic records often contain fields with lengthy content. E.g. Table of contents (505); Notes (520). This can make the Full Display very long. While the data in these fields are important, they are not necessarily helpful to always show them to every single user. Options to hide/expand fields in the Details section should be available with links like "show table of contents"; "show full description". Institutions should be able to specify how long the field is before collapsed appearance/link applies. | It would improve usability if long fields could be collapsed in the full record view with a link to "show full record", or links like "show table of contents"; "show full description". | Improved user experience |
7693 | Add ability to prevent CDI expansion of results (VE/BO) | (VE/BO) | The ability to control your search query is fundamental to successful discovery. In the design of the Central Discovery Index (CDI) this is not possible, as term inflection expansion of results is constantly applied to all searches. Our users have no autonomy to prevent this by using techniques such as quotation marks, Boolean operators, or the 'is (exact)' search type in Basic Search pre-filters or Advanced Search. This is a downgrade from the Primo Central Index (PCI), where results were presented which respected that a user knows what they want when using more specialised search techniques. |
|
|
7697 | Better UX for placing requests (VE/BO) | (VE/BO) | Our patrons struggle with different aspects of the requesting workflow. 1) When a book is available on the shelf in open stacks, our on shelf request policies do not allow pickup locations anywhere, but are restricted to different library or campus. This limits the pickup locations that are offered for selection, but there is no explanation for the user as to why they are limited. In our older discovery system there was a pop-up note informing the patrons that they should fetch this item in the open stacks themselves. We'd like to show such a note again (by form or pop-up). This note should appear only when the item is not on loan, after a user clicks on the request option link. The existing possibilities via labels do not meet this request as they appear on all hold request forms regardless of the on shelf request policy. 2) When a book can only be requested to the reading room of the owning library, the interface skips a step and pre-selects this as the pickup location. The intention may be good (save the patron some clicks), but the result is very confusing because it is inconsistent with the usual steps and the patron places a request without understanding that a pickup location was assigned automatically. 3) The choice for home delivery needs to be parallel to pickup location. The two are mutually exclusive. | This has two annoying aspects for our patrons: a) in the milder case, it only costs them time, because they pick another pickup library and then have to wait for the book to arrive there. b) it can also cost them money that they could save: we know of cases where patrons did a request to have a book sent home because the interface does not explicitly let them know that they can just fetch it from the shelf themselves. | Make the requesting workflow less confusing/frustrating for the patrons. |
7698 | Consortium: show facet 'Other libraries' only in NZ search profile (VE/BO) | (VE/BO) | For most facets it is possible to decide in which search profile they should be visible, at which position and if it should be collapsed or not. These options do not exist for the facet 'Other libraries' in a consortium. Our search profiles are 1) IZ only = libraries in Basel; 2) NZ = libraries in Basel, plus CDI. We show the facet 'Library' in both search profiles. The facet has an option to "show other libraries"; when we activate this, we get an additional facet "Other libraries", but there is no way to adapt it to our needs: we want to show all libraries in our consortium, but only when the search profile is "libraries in Switzerland" NOT when the search profile ist "libraries in Basel". There is no way to achieve this at the moment. 173 votes in idea exchange . | . | This needs to be possible. |
7699 | Physical item sort routine: allow distinction between journals and monographs (VE/BO) | (VE/BO) | Physical items sort routine by date - enable I J K descending, but A B C ascending. We're running into a problem with the Physical items sort routine - Sort according to date: For journals, we want to sort the latest item on top, this works correctly with "Sort according to chronology I/U/K (year/month/day) - Descending", Example https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma9910177740105504&lang=en&context=L. BUT: The same sort routine is also used for multi volume monographs. We found out that if we only fill out conditions for Chronology I J K, but those fields are empty, the barcode gets used for sorting. Which leads to wrong sorts. So we had to add "Enumeration A, B, C" as a condition. This leads to a display where volume 1 is last in the list. This is not what we want. Example: https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma993749450105504&lang=en&context=L. It should be possible to sort A, B, C ascending, while I J K are sorted descending. |
|
|
7700 | Better UX for changing number of titles per page (VE/BO) | (VE/BO) | It's good that we now can see more than 10 titles per page. But when switching from 10 to 25 or 50, a) the display should neither jump to the top of the page nor jump anywhere else in the list: when I switch from 10 to 50 titles, the titles that I see next have to be title 11 ff.; b) the display of the titles should not 'slide in' because the icons load later and need more space. This is not happening when the setting is 10 titles per page. c) Switching from 10 to 25/50 should also be possible at the top of the page, not only at the bottom. // Number of titles per page should be a setting in the patron's account. // Setting the default number of pages to at least 25 (rather 50) should be doable per view. |
|
|
7701 | Ability to collapse the sections in full title display per view and per search profile slot (VE/BO) | (VE/BO) | Please add the ability to collapse each section in full title display, configurable per view and within the view per search profile slot. Example: We are in a consortium, and some information in the full title display is confusing for our patrons and we have no way to hide it. We have a search profile "our IZ" and a search profile "NZ & CDI"; the section 'Other loan and request options' should be collapsed in "our IZ", but expanded in "NZ & CDI". |
|
|
7706 | Add ability to specify a default sort order for list of items associated with a holding in Get It section of full record display (VE/BO) | (VE/BO) | When there are many items available for a given holdings, especially for serials (journal, newspaper) with many volumes/issues, the items sometimes don't display in chronological order. This can hide the newest issues available and force the end user to use the filter option (which they sometimes don't see at all) to find the issue they're looking for. | https://catalogue-bsb.sorbonne-nouvelle.fr/permalink/33USPC_BSB/17flepn/alma990000780680605803 |
|
7712 | Allow patrons to request a specific item in a fulfillment network (VE/BO) | (VE/BO) | We are in a consortium with a fulfillment network which in many cases means that the patrons can not pick which copy of a book they want to request. While this may make sense as the default, it is frustrating for many patrons and for library staff trying to help the patrons. a) When there is more than one copy, it should be possible to place the request on a specific copy, overriding the default setting. b) When a book is on loan I may prefer to wait for the copy of my favorite library to come back instead of getting the book from somewhere else. This is especially relevant when I'm in a setting where getting a copy from another library costs me money. |
|
|
7714 | Music discovery - Name/Title Browse Searches for authorized headings (VE/BO) | (VE/BO) | As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors. |
|
|
7728 | The possibility to change the order of values in the top-level facet (VE/BO) | (VE/BO) | Have the ability to change the order of values in the Top-Level Facet (facet_tlevel) per view as the institution decides. For example: 1. Available in the Library; 2. Full Text Online; 3. Peer-reviewed Journals; 4. Open Access; 5. Cited Articles. |
|
|
7733 | Provide "Save query" functionality for zero results searches (VE/BO) | (VE/BO) | Add the "Save query" option to zero-results pages (similar to how it already appears on results pages) for when you want to be notified of expected future results. For example, you might want an alert for a recently published article not yet in CDI, or an emerging topic that nothing has yet been written about. | Currently 'zero results' searches cannot be saved. | An effective way to extend the use of existing functionality and improve the service. |
7734 | Adjust CDI Match & Merge to preference surfacing of primary publisher scholarly records by Article type (VE/BO) | (VE/BO) | CDI Match & Merge combines participant records of more than one type, such as the same Article supplied to Ex Libris by three providers, where two of the providers indicate the work is a Text Resource and the third indicates the work is an Article. It is not uncommon for providers to incorrectly type resources only as Text Resource, when there is clearly information in the record which indicates the work is an Article, particularly from providers no longer updating content or third party aggregators with policies to not manipulate content themselves. Both of these are understandable, but still result in a Primo environment where users may unwittingly filter out the resources they need when choosing to filter by Articles. It is known from CDI fixes in 2020 that current CDI design incorporates an algorithm to surface a single type for the logical record based on "popularity". In the example, the result is that the Article appears in Primo incorrectly as a Text Resource, by measure of two versus one. Ex Libris has advised that they have no current plans to improve the algorithms to correct types at scale, due to large variations across provider data and often insufficient standardised specific information across collections. Instead, Ex Libris has suggested that the pathway to improvement is an enhancement request to build in an algorithm which selects the more scholarly type over the more general type where there is more than one participant record. For example, to preference Article over Text Resource as the logical record type which appears in Primo, even if it is not the most types for the work by "popularity. It is also mentioned in discussions with Ex Libris that this could result in undesirable changes, so an alternative and likely safer option could be to preference the resource type supplied by the primary publisher source, over sources such as aggregators. Or perhaps a mix of these two concepts together. This enhancement will certainly need to be carefully built, but it is proposed that this is a worthy area to enhance as leading to a more useful Primo environment for users in identifying key scholarly Article resources correctly. | BACKGROUND
| IMPACT
Inaccurate content types impact this strategy, causing potentially highly relevant content to be missed, and delivering a substandard experience to the user.
If this information could be repurposed to privilege journal articles content type over more general content types in the same logical record, that might make it possible to alter this display on a large scale without impacting records which are correctly labelled as text resources. |
7735 | Sort search results by citation count (VE/BO) | (VE/BO) | We greatly appreciate existing Primo functionality for citation counts, with Times Cited from Scopus and Web of Science and links to these source platforms. We'd like to see more done in this area within Primo itself to highlight and utilise this valuable data, and suggest to be able to sort the search results by the citation count. It would be useful for both staff and users alike to be able to sort search results from most cited to least cited. This could be by both of the existing sources of Web of Science and Scopus, by the greatest count in real time calculation, which would remove the need to account for duplication if multiple sources are used. In order to ensure this feature is meaningful for users, there should also be an indication added to record display to advise the citation count which has resulted in the changed ordering. This could be via an additional display element, or an adjustment to the existing Times Cited display. | In a large results list this would be the most efficient way to identify which results are the most highly cited. | A basic tenet of librarianship is to save the time of the user. This suggestion will deliver more efficient functionality to the user in wrangling large sets of search results. |
7748 | Filter the pickup locations in the Request form (VE) | (VE) | A Primo view can be associated to one or several libraries through the mapping table "Primo views to libraries". |
|
|
7749 | Allow enrichment of local subject fields (VE) | (VE) | Currently Primo VE indexes non-preferred (4XX) terms in the basic search and in the default Subject advanced search only. We would like to have an option in the Customer settings to allow indexation of preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records for the locally defined subject fields. Alternatively, enabling this option could enrich the Primo VE bib records with those terms (in the same way an option allows the enrichment of bib records in the publication profile for Primo BO). When a library selects this option and creates local fields, then the advanced search on these local fields would return relevant results enriched with the 1XX and 4XX fields from authority records. |
|
|
7750 | Authority record enrichment for Classification authority records (VE) | (VE) | Currently in Primo VE, classification caption in field 153 $j as well as fields 7XX of classification authority records are not indexed. We would like to have an option in the Customer settings to allow indexating of 153 $j as well as 7XX fields in related Alma classification records. Alternatively, this option would enrich the Primo VE bib records with those terms (in the same way an option allows the enrichment in the publication profile for Primo BO). |
|
|
7751 | Add other call number types to Browse Search (MARC21: 852 i1 = 7) (VE) | (VE) | Currently in Primo VE the Browse by call number type "Other scheme" works only with 852 i1 = 8. It is not possible to browse by call number on 852 with i1 = 7 at all, contrary to Primo BO. The "callnumber" (Other call number) Browse Type from the View configuration should include all other call number types, including "Source specified in subfield $2"(i1 = 7), or a specific Browse type on call number type 7 should be added to cover this specific case. |
|
|
7752 | Improve availability status in Brief Display in a filtered Primo view (VE/BO) | (VE/BO) | A Primo view can be associated with one or a few libraries. In such a view, the locations are filtered in the Get section. However, in the record display brief, availability is calculated over the entire institution, not just in the view's library. We want availability to be calculated only in the library associated with the view, which is what patrons expect. |
|
|
7756 | Display of physical item's holding range in the form of ‘from … until ….” in the Location list (VE/BO) | (VE/BO) | The Primo holdings display shows the summary holdings, such as 852 and 866. However, when we enable this feature, the item range in the form of "from … until …." is no longer displayed in the Location list. We would like the ability to display both the summary holdings AND the auto-calculated item range ("from... until...") in the Location list. |
|
|
7757 | Include total number of pages for exporting to RIS/Mendeley (VE/BO) | (VE/BO) | There are some citation styles which require a total number of pages to be included for accurate referencing. However, Primo does not currently export the total number of pages to RIS/Mendeley, whether because there is no total page in PNX or the field is not mapped. Therefore, we would like all records to include pagination information and be exported as expected with this data to ensure citations are accurate, regardless of record source, such as from CDI or from local records by 300a. |
|
|
7780 | Display item policy in item record (VE/BO) | (VE/BO) | It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user. |
|
|
7783 | Several items in a single request (VE/BO) | (VE/BO) | "It seems critical to make the request service evolve in Primo (and Alma for the tracking). |
|
|
7790 | Requesting Flexibility in Local Resource Type Configuration (VE) | (VE) | Local resource type configuration was much more flexible in Primo Back Office than it is in Primo VE. We are requesting a restoration of that flexibility under Primo VE via the following three components:
| For example, for certain textual integrating resources that users are likely to think of as books (such as some open textbooks), we use conditions based on the presence of form/genre headings to add them to the OTB "book" display type in Primo BO. Some institutions would like to exclude monographic series from the OTB "book" rule. Others would like to be able to remove conditions related to 007, since these often refer to accompanying material. | Providing flexibility in this way will allow institutions to categorize materials to meet the needs of their local users. |
7796 | Extend lateral links for Relation, Is Part Of, and Uniform Title beyond local records (VE/BO) | (VE/BO) | Clickable lateral links for the ispartof, relation, and unititle fields were introduced in 2017, for NERS #5291 as part of "Enhanced Hypertext Linking". These new fields joined existing lateral links for creator, contributor, and subject. However, a key difference for the three newer fields is that they are only clickable lateral links for local records and while they are found displayed in CDI records, they are not clickable. The restriction of some lateral links to only local records causes confusion, with questions as to why some records are missing these links, which lead so helpfully into Advanced Search showing all records with this data in one cohesive results set. This is a disappointing inconsistency in our blended scope environment, especially when we see through our Primo Analytics data that lateral links are a popular feature, with thousands of clicks every week. An example use case are Relation fields for works in a series, where there may be local book records and book chapter records from CDI (example: Advances in Biochemical Engineering/Biotechnology). The outcome of this enhancement request would be for the Relation, Is Part Of, and Uniform Title lateral link fields to be consistently clickable in the full record display for all records, regardless of data source. |
|
|
7797 | Authority record enrichment for Established Headings (VE) | (VE) | Support for indexing and displaying Established Headings 7XX fields from Authority records. |
|
|
7799 | Add facets similar to simple/advanced search results to Collection Discovery interface (VE/BO) | (VE/BO) | We suggest adding facets to the Collection Discovery and having the ability to choose which facets to display and how their values will be sorted, just like on each tab of any view. |
| There is also an IdeaExchange that got 125 votes already: |
7801 | General Electronic Service - Additional Display location for View It (VE) | (VE) | It's possible to set up a General Electronic Service (GES) to display in Primo under: |
|
|
7809 | Enable patrons to check 'Keep me signed in' (VE/BO) | (VE/BO) | Our patrons are frustrated that they get logged out after a relatively short time. It is quite a common feature to be able to check "Keep me signed in". In Nili Natan wrote in 2017 "We examine the option for providing 'keep me logged in' in primo." This should also work when the patron's authentification runs via an external service. |
| Patron feedback via twitter. |
7813 | Filter Resource Type by Magazines in Primo (VE/BO) | (VE/BO) | We would like the ability to distinguish between journal and magazine article/resource type when searching in Primo. We would like for our users to be able to easily identify or search for just magazine articles. Being able to search by magazine resource type would be advantageous to all of our students. This option is available in Ebsco searches, so it seems like this could feasibly be implemented in Primo. | Being able to filter resource type by magazine would allow users to more easily identify and search directly for magazine articles. Currently, magazines are grouped in "articles" which can be confusing particularly if journal and peer reviewed articles appear at top of search results. | Our users are community college students with varying levels of information needs. Users could be completing advanced coursework, basic skills coursework, or students could be English language learners. In some of these cases, journals are not appropriate or relevant for the assignment or user's need. This feature would not just serve community college students, but students in 4-year universities, as well. I've seen this request in Idea Exchange, so I also know that other libraries would like to see this feature become a possibility. |
7820 | Add A-Z to Database Search (VE) | (VE) | Primo VE does not have an A-Z in Database Search. This is a parity issue, as this feature is available in Primo managed via Back Office. Ex Libris has stated that this is a design decision because they believe users see an A-Z as outdated. This opinion is not reflected in evidence in Primo Analytics, with up to 3,300 clicks per month. |
|
|
7821 | Show facet counts for top level and new records (VE) | (VE) | Primo VE design hides facet counts for top level facets and the new records facets. Our users report to us that seeing a count against facets gives meaning to results, and entices them to use the facet, as they can clearly see the outcome of their action by the stated number of results. This meaning is not significantly lost by minor variations for grouped records. This is a parity issue, as this feature-rich functionality is consistently available for users in sites with Primo managed via Back Office. |
|
|
7822 | Add ability to create new mapping tables for use in normalization rules (VE) | (VE) | Primo managed via Back Office has powerful functionality to reference source data by normalization rules against custom built mapping tables and normalize accordingly from source data to target data. This has benefits for consistent display in full records, able to be used also for lateral links that bring together all records regardless of source data variation, as well as the same benefits in cohesive facets. It also enables addition of underlying search data to support return of results, such as if source data is a term which a user may not include in their query such as 'BAHons', as this can be mapped to add meaningful terms which a user is more likely to have in their query, such as thesis, honours, bachelor, bachelors. Sites can also collapse into one similar locations for multiple libraries by such mapping tables, such as all 'Stacks' locations grouped together. There are endless use cases for how sites can improve their Primo environments through dynamically built mapping tables, to meet the needs of their users and their collections. This is a parity issue for Primo VE, and it should offer the same full configuration functionality as Primo managed via Back Office. |
|
|
7823 | Allow normalization of MODS records to Primo (VE/BO) | (VE/BO) | Key data is missing from our displays, and we look bad to patrons and other librarians. Much data is lost, including all personal names. In the example below, for a digitized concert program, the name of the guest conductor, who is also the composer, does not display in Primo. In the original MODS, the name is included as both a conductor and a composer which does not display to the patron in Primo. |
| There should be options to configure the display of MODS fields just like there are for MARC fields. MODS is an important schema for describing digital materials. There is a great deal of data in the records which can be parsed fairly easily, but right now we can't view or edit the rules to see how it is being parsed or make changes to the display. |
7824 | Add ability to manipulate availability statements and GetIt by Delivery and Scoping and Links rules (VE) | (VE) | Primo managed via Back Office has powerful functionality to adjust availability statements and GetIt by Delivery & Scoping rules and Links rules for all harvested data sources. |
|
|
7825 | Add ability to add and adjust top level facets (VE) | (VE) | Primo VE currently does not permit addition or adjustment of top level facets other than to disable them or hide them by customization package. Primo managed via Back Office has full ability to adjust top level facets for local records by the facets_toplevel rule specifically for just this purpose for all local data sources. We have utilised this functionality, with examples such as adding a top level facet for all Alma 'Physical Items' by Alma-P, instead of only the out-of-the-box facet value for available physical items, to blend all Alma records with a local fields of lds50 of peer-reviewed with CDI records in the Peer-Reviewed facet, and for all Institutional Repository and Archival Management System records by linktype for either fulltext to blend with the Available online facet or linktypes such as notonline to add a new top level facet of Access conditions apply (married with the may_be_restricted availability statement). We also configured relevant Alma and Institutional Repository records to blend with the Open Access CDI records years before it was done out-of-the-box by Ex Libris. This is a parity issue for Primo VE, and it should offer the same full functionality as Primo managed via Back Office for all records (including Alma records, discovery import profile records, and Remote Digital Repository records). |
|
|
7828 | Extend the limit on the Summary Holdings Display to more than 10 holdings (VE) | (VE) | Description: If a title is held at more than 10 locations, its holdings summary which covers important information like range of coverage will not appear on the Locations page—however, the more locations, the higher demand for checking the titles coverage. Therefore, please display all summary holdings regardless of the number of holdings. |
|
|
7829 | Display 3 items from the three dots menu in the My Favorites (VE/BO) | (VE/BO) | In the list of saved records in the patron account it is not clear that there are actions that can be applied to multiple selected items in bulk. |
| Currently, a patron cannot know what actions are available for a selection of their favorites through the hidden menu in the Favorites screen. |
7830 | Permalink as added Action to My Favourites action menu (VE/BO) | (VE/BO) | Permalinks are currently only available for individual records. It would be useful to have a similar link option for a bulk selection of Saved Items in the My Favourites action menu. This would allow for users to select multiple items in My Favourites, such as many resources organised by label, and provide the permalink to this targeted set to another user. Clicking on the link would generate a basic search into Primo containing only those specific Saved Items. |
|
|
7835 | Add the "Library" index in the advanced search (VE/BO) | (VE/BO) | "Library" is only available as a facet. It would be useful if "Library" could be also available in the advanced search, like language or resource type. This type of research is used more than one would think and our patrons regularly ask why it is not possible to limit the results directly at the library level, using this search mode. |
|
|
7836 | Add the Open Access indicator to CDI records where there is a link in the Links section for a known Open Access source platform (VE/BO) | (VE/BO) | CDI records are marked in Primo as Open Access by varied means, including at the Collection level and at the individual record level. The Open Access indicator controls whether or not the URLs displayed in the Links section of CDI records are proxied or not, per site configuration with the "Do not proxy Open Access records" setting. This causes an issue with the nature of CDI Match and Merge design, as the logical record presented to users may not include this Open Access indicator due to being from a subscription based source provider, despite that there are participant records which are from Open Access sources, and their links are presented in the Links section. This leads to a situation where sites have an additional significant workload to configure access in their site's proxy server for open access resources. It is proposed that Ex Libris add the Open Access indicator to CDI records where there are URLs displayed in the Links section from any Open Access participant records or otherwise adjust the mechanism for these Links to not be proxied when from a known Open Access provider. |
|
|
7838 | Display block expiration date and block type information in block section of user Account (BO) | (BO) | On primo BO used in connection with Alma, in the user account (My account), the "Blocks + messages" section currently only displays the indication that the user is blocked, without any further indication. | A ticket was open on this matter by Ecole Normale SUpérieure in France: #06255176. |
|
7839 | Full Text Available in full record should take users directly to the resource (VE) | (VE) | "Full Text Available" link in the Full Display should take users directly to the resource. An example video can be found in the NERS request. | I am an OU student using Library Search (Primo VE). When in Brief Results, "Full Text Available" takes me directly to the resource. But when I am in Full Record, it scrolls my screen down, I find it really confusing. I would like "Full Text Available" in full records to take me directly to the resource. | The Open University conducted UX testing with users, users expressed that they would like "Full Text Available" in full records to take them directly to the resource. |
7840 | Need a Newspaper Titles Facet in Newspapers Search (VE/BO) | (VE/BO) | The Journal Titles facet has a universal label that is not appropriate for Newspapers Search, where the source publications are newspapers and not journals. It should be possible to use a different label in Newspapers Search, identifying the source publications as Newspaper Titles and not Journal Titles. | Correct labels are important for all researchers; incorrect labels are especially problematic for less experienced researchers. | Users are very confused when they see the "Journal" label within the Newspapers Search interface. They know they are trying to search for newspaper articles, and they don't understand why Journals are then suggested within the facets. In fact it is Newspaper Titles that are available in the facet, but they need to be labeled as Newspapers for users to understand that and make appropriate use of the facet. Some instructors have stated that they would avoid teaching students to use Newspapers Search because of this confusion - it is very difficult to explain to inexperienced student researchers why Newspapers are labeled Journals in the facet. |
7841 | Add option to display all fields in static deduped records (VE/BO) | (VE/BO) | When dedup is enabled, one can choose to display a preferred record by type of inventory, such as Alma-P or Alma-E. There is also the option in Primo VE of None for no preference, with the result being a dynamic record selection of the best matched record to the search query. With the current available options, fields from the non-preferred records are hidden from display. We propose to add an additional 'No Preference Static Display' option. When this option is chosen, the displayed record is consistent in presenting all the available data, and is not variable depending on match to the search query. |
|
|
7843 | Relevancy sorting in FRBR version list display should use terms searched (VE) | (VE) | FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. | The search for versions of the Iliad translated by Lattimore provides a good example for the need for improvements to this functionality. Many institutions hold numerous different editions and translations of Homer's Iliad, resulting in FRBR groups with potentially hundreds of records. It is currently exceptionally difficult to locate particular known items within these groups. This problem occurs with all large FRBR groups. | Impact of Problem: Our users are extremely frustrated and ill-served when they are unable to locate the specific versions of works they need because these works are buried within large FRBR groups. They often give up and either assume we don't hold the materials they need or turn to Google or other sources instead. Our only remedy at present is to turn off FRBR grouping, either selectively for individual titles, or for the whole system. The first option, selectively suppressing FRBR for certain titles, is a very cumbersome process that can easily miss content and is also complicated for consortia, who need to apply rules for both IZ and NZ, in an environment where different institutions may have differing FRBR needs. The second option, disabling FRBR completely, then doesn't allow us any of the advantages that FRBR grouping might otherwise present. |
7845 | Include call number for physical items in Excel / CSV Export (VE) | (VE) | The Export to Excel option is a great enhancement for Primo record actions that is very valuable and much used by researchers. However, one critical area of data is not available for export in Primo VE: physical holdings information, such as Call Number and Physical Location. This data can be added to the AVA field for Primo BO, but there is no equivalent configuration for Primo VE. | Primo users need details such as library location and call number in their Excel exports so they can use these files to locate materials. | Impact of Problem: Researchers often Export lists of records that they then wish to find on library shelves -- but they need the Library Locations and Call Numbers to do so. We have received many complaints from researchers unhappy to find this info missing from their exported Excel files. Adding Physical Location and Call Number to Excel Export fields in Primo VE would more completely meet the research needs that this functionality is designed for. |
7847 | Enable creation of Carousel widgets for collections (VE/BO) | (VE/BO) | We would love to be able to create scrolling carousels to highlight collections, and embed them in other platforms (LibGuides, webpages, etc.). We see examples of this kind of carousel within Primo records, for materials that are in Collection Discovery (aka Digital Collections); at the bottom of the record there is a feature labeled "More from the same collection" with a link to the full collection in Collection Discovery as well as a scrolling carousel of cover art images with links to the other titles. We would like to be able to embed this kind of feature in other resources. | Institutions need to promote their materials to users, often requiring outreach via other platforms. A carousel of cover art images with links to Primo records would be a very appealing and attention-grabbing way to increase use both of the materials and of Primo itself. | Primo's Collection Discovery is a very appealing feature, as are the carousels that are displayed within Primo records for "More from the same collection". Being able to use these collection-oriented carousels in other locations would really highlight and promote our Collection Discovery, making the tools even more valuable. |
7848 | Combine Two or More Recent or Saved Searches (VE/BO) | (VE/BO) | Users should be able to select sets from their Search History or Saved Searches and combine them using standard operators such as AND, OR, and NOT, with the system then processing and presenting a new set of search results based on the interaction between the selected sets. |
| Other Proquest search tools include this functionality, with documentation available at |
7851 | Add ability to select multiple options on Advanced Search drop down menus (VE/BO) | (VE/BO) | It is not currently possible to select multiple options on an Advanced Search drop down menu in Primo (ex: Material Type, Language); this functionality would be very helpful for users who wish to do more precise searching -- especially since Primo lacks the functionality of combining search results. This functionality is the HTML select multiple attribute ( ) |
| Researchers often wish to perform precise searches based on several limiters. For example, they may wish to search specifically for more than one material type (books, conference reports, dissertations, etc.), while excluding other types. With current system functionality, they must perform several searches, one for each criteria. Being able to select multiple options would save time and make searching more efficient, greatly benefiting the researcherd in other systems and expected by users. It would also bring system functionality more in line with that encountered in other systems and expected by users. |
7852 | Enable Public Notes display for content within Link in Record collections (VE/BO) | (VE/BO) | It would be very helpful if Public Notes could be displayed for individual content (articles, etc.) within Link in Record type collections. Currently, Public Notes for Link in Record type collections can only be placed on the record for the collection itself, and they are not displayed on CDI records. This functionality is in place for Link Resolver collections. Public Notes can be placed at the individual portfolio level or at the collection/service level to display on all portfolios and CDI records. This functionality would be very helpful for Link in Record type collections as well. | Currently, if a user searches for the name of the database (such as ProQuest Congressional Hearings Digital Collection: Part A (1824-1979)) they can see the Public Note below the View Online link -- but if they search for an article held within that collection (such as Committee Business. Congressional Hearing, 1980-07-31), there is no public note displayed with the View Online link. The info we communicate in Public Notes is most often needed for accessing the individual content. | It is very helpful for institutions to display public notes about collections within Primo -- these notes can provide important information to the user about special instructions needed for specific collections and other specialized help. These notes need to be displayed at the point that users see and will follow links into the collection -- that is, at the article level. Public notes can be displayed at the article/content level for full text collections, but not for database-type collections. For database-type collections, the notes only appear at the database-level, which is not the level from which users typically link into the collection. Enabling public notes at the article-level for database-type collections would bring the functionality of these collections more in line with the existing functionality of full text collections, which would be a boon for users. |
7853 | Highlight one result from each Resource Recommender type in brief results (VE/BO) | (VE/BO) | We can create multiple types of Resource Recommenders, but if multiple items within a particular type match the tags a user searches for, multiple items are returned from a single Recommender and some Recommenders are hidden. We would like to be able to highlight one result from each matching Recommender. | Display in Primo seems to support highlighting 3 items from Resource Recommenders in brief results, with additional items displayed under a link to "See all [#] suggested resources." We currently have three Recommender types: Library Guides, Databases, and a Custom recommender for Librarians (enhanced version of Person recommender). No matter what type we move to the top of the list, if the tags are assigned to multiple items within a recommender, then 2 items may be displayed from the 1st or 2nd Recommender, with no results from the 3rd, effectively hiding the 3rd Recommender within the "see additional" link. We would like to highlight one result from each Recommender type -- a Library Guide, a Database, and a Librarian -- in brief results, so that researchers are aware of all available Recommender types. | We are pleased to be able to create three different types of Resource Recommenders, and we make great use of all three. All three types are very important to support the needs of different researchers, who benefit greatly from these referrals to Databases, Research Guides, and Librarians. However, currently only two of the three types can be displayed in initial search results -- even though there are three spots for Resource Recommender entries. The third type is always hidden under the "See all ... suggested resources" menu, so researchers may not even be aware that there is another type of resource to help them. Being able to highlight one result from each of the three types of Resource Recommenders would make all available types immediately accessible to the researchers, better filling the needs of all types of researchers. |
7855 | Add filter for "Available Now" (i.e. not checked out etc.) to Availability facet (VE) | (VE) | The Availability facet in Primo currently includes options to limit by "Available online" and "Held by library". It would be helpful if these options could be further refined to enable filtering to materials that are actually currently fully available/accessible -- for example, not checked out to another user or in another out-of-library processing status. This functionality can be found in other library search tools – for example, Overdrive includes an "Available now" filter. | Researchers working on tight deadlines who need ASAP access to materials are helped by the ability to filter to "Available online" but stymied by "Held by library" results that include physical materials that are checked out or otherwise not available. | Users often want materials that are most immediately available to them. This need is partly met by faceting to content that is "Available online." It would be more fully met by being able to filter by facet to non-online materials that are held within the library that are available for loan (i.e. not checked out or otherwise out of circulation). Users are frustrated when they try to narrow their results to available materials when they find those materials are in fact checked out and not immediately available. |
7857 | Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation (VE/BO) | (VE/BO) | In our consortium, when filtering the search results list to a certain library via facets, we often get results that the chosen library does not own, which is unexpected from patrons' perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. This behaviour is correct for analytical records without inventory (book chapters and articles), but not for the other monographs.
Right now, the configuration possibilities do not offer the needed flexibility. |
|
|
7859 | Add barcode search to Primo (VE/BO) | (VE/BO) | It would be useful to be able to search by item barcode within Primo. This would enable our users to locate specific physical items on the shelves more easily. Also, our student-facing staff, not all of whom are Alma users, would find it helpful to be able to search for items by barcode in Primo. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand, without needing to key in the title or ISBN. The barcode is stored at the item level in Alma, where it should be, and is therefore not available for search by any current mechanism for search on bibliographic or holdings data. We would like an enhancement to Alma discovery and publishing which would add the item barcode to the data available to Primo for return of results. We understand that colleagues elsewhere are also keen to see a barcode search functionality added to Primo ( ). |
|
|
7864 | Newspapers Search interface and functionality (VE/BO) | (VE/BO) | The Newspapers Search interface is lacking in many features and functions that are present in Primo Search. The system should be improved so that features and functionality are consistent across these interfaces, and it is possible to search in Newspapers with the same granularity and specificity as other Primo Searches. Needed elements include: Advanced Search; ability to save, pin, and act on multiple records; inclusion in Search History; user-friendly record IDs and permalinks; search term passage between Primo Advanced Search and Newspapers Search; troubleshooting tools such as CDI Activation Analysis tool. |
| Users rely on common search functionality (such as Advanced Search) to accomplish their research needs efficiently and effectively. They learn to use Primo and appreciate its functionality. Newspapers Search currently presents many obstacles to efficient and effective research because it lacks core functionality; users can not search in Newspapers as they can in Primo, and this is confusing, challenging, and disappointing to them. Often they seek other routes for Newspaper content because of the system problems. |
7869 | My Account - Loans Sort Options (VE/BO) | (VE/BO) | User should be able to sort their loans not only by title and due date, but also by author, location, maximum renewal date and status (renewable or not) -- all columns shown should be sortable. This same idea on Idea Exchange has many votes already: |
|
|
7870 | Add ability to change default sort for results (VE/BO) | (VE/BO) | I would like to change the default sort for one of our views from Relevance to Date-newest. Our library has a lot of grey literature which is not handled appropriately by the Relevance sort. |
|
|
7871 | Newspapers Search content needs to distinguish between different editions (VE/BO) | (VE/BO) | Newspapers can be published in multiple editions, all of which use the same ISSN, with relatively minor changes in article headlines and content between these editions. Since the same ISSN is used, Newspapers Search currently includes all content associated with a single ISSN -- but the source content providers may carry only particular editions, and not all editions. The inability to match on both ISSN and edition results in metadata mismatches and link failures when Newspapers Search records provide links to content in aggregators that don't include the specific editions. An example of this is the New York Times, ISSN 0362-4331, which publishes a Late Edition with articles that are often changed when published in the Daily Edition. An aggregator often includes only the Daily Edition, but Newspapers Search includes records for both the Late and Daily Editions, with links for both going to the aggregator. | Much newspaper content is published online with a paywall; libraries subscribe to newspaper content through various vendors and aggregators to provide users access to this content through institutional access, with Primo Newspapers Search providing the platform for access. When users search in Newspapers Search and encounter records for content that isn't actually available with links that don't work, they get frustrated and believe that the system is just bad. Users give up on the library systems and subscriptions, going instead to Google or a site in which they have to pay for content. This problem blocks user access to content that institutions invest in very highly. | It is extremely frustrating for users to encounter bad links to content, and these particular bad links provide no means of troubleshooting for the user, since the records are consistently providing links to inappropriate collections. Records in all areas of Primo -- including Newspapers Search -- should clearly, consistently, and accurately identify whether materials are available online and in which collections, with links to those collections. This is very basic and critical system functionality. Currently, Newspapers Search is including an unacceptable number of records that are not available full text online within "filtered by availability" results, with inaccurate links to collections in which the articles are not really held. The current inability to distinguish between different editions of major newspapers is one reason for the problem which needs to be addressed. |
7873 | Report on external data sources via Primo Analytics (VE) | (VE) | Analytics for Primo BO includes a subject area for Primo Pipes, which allows reporting on data sources piped into Primo. The same subject area is not available for Primo VE, meaning we cannot report on any external data sources. This would be useful for monitoring external records in Primo and allow headline figures for number of records in a particular data source, for example. |
| This would be useful for monitoring external records in Primo and allow headline figures for number of records in a particular data source, for example. |
7878 | Resource type: article reviews (VE/BO) | (VE/BO) | Our users cannot distinguish between "articles" and "articles reviews"; all are on the same resource type "articles". |
|
|
7885 | Add a resource type for abstracts in CDI (VE/BO) | (VE/BO) | CDI contains many records for abstracts of papers presented at conferences which are inaccurately described as "Articles." This practice is not only misleading but also generates many false error reports from users complaining that they are unable to retrieve full text only to be informed that the abstract is in fact the full text. |
|
|
7886 | Improve discovery and access for journal articles which are in-press, within special issues, or online only (VE/BO) | (VE/BO) | CDI provides many discovery records for in-press journal articles (i.e. articles that have been accepted for publication in a forthcoming issue), articles in special issues, and articles which are online only. Such articles often lack full publication details, including missing issue, volume, and date information, or may simply be excluded from collections. This poses a problem in terms of both the initial matching of electronic holdings coverage to CDI records to ensure that the records are correctly marked as full text or not, and then in providing a stable link resolver openurl link directly to the full text content. We ask that Ex Libris improve the user experience for this type of content, whether this be through initial CDI record matching, Link Resolver improvements, switch to Link in Record, or if there is no possible avenue of this nature which retains discovery records, consider removal of such content from the index. One example is Ahead-of-Print articles in Taylor & Francis (Example: ); another example is conference reports and other specialized content excluded from PubMed. |
|
|
7888 | Ability for users to change facet sort on the fly (VE/BO) | (VE/BO) | Facets can be set to sort by size or alpha-numeric in the View. We would like users to be able to change the sort method on the fly in Primo, since the chosen "default" sort isn't best for all situations. | For example, on a Creator facet that is sorted by size, switch to sort by alpha in order to see name variations together. | Researchers use the facets to help narrow their search results. Libraries pick a default sort option that seems most generally useful in a broad number of cases, but for any individual researcher in any individual search, the other sort option may be more helpful. |
7891 | Display multiple addresses in Personal Details tab within My Account (VE/BO) | (VE/BO) | Users may have multiple addresses in Alma. The Personal Details tab within My Account only can display one address, the preferred address. The display of multiple addresses should be configurable. | Users are unable to review all of their addresses in My Account which can result in errors when an incorrect address is mistakenly selected in Personal Delivery. If all addresses could be displayed in My Account, users could see and correct any mistakes. | Users often have multiple addresses (home, work etc.). When users are unable to review all of their addresses, one or more addresses may be incorrect, consequently going undetected by the user. When selecting addresses for Personal Delivery, items may be sent to an incorrect address. This results in poor customer service for the user and losses for the library. |
7893 | Ability to specify which 856 (MARC) fields display in Links service (VE) | (VE) | In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 MARC fields display in the "Links" section of the Primo full record view. It is crucial to user experience to have a similar functionality in Primo VE to customize which 856 links to display, based on regexp (regular expressions) and 856 first and second indicators and subfields. |
| An overwhelming variety of links are added to 856s for both physical and electronic bibliographic records: the resource itself, other versions of the resource, finding aids for archival collections, TOCs, cover images, summaries, reviews, excerpts, etc. For electronic resources, despite provider neutral record guidelines, many institutions still add local proxied links to OCLC records. With the volume and variety of 856s in both print and electronic records, an all-or-nothing approach to displaying these links leaves only two unsatisfactory options: either displaying none of these links, or displaying a frustrating and overwhelming amount of potential links of varying relevance to users. |
7894 | Display physical inventory from other consortial network institutions in deduped records when local institution has electronic inventory (VE/BO) | (VE/BO) | Describe the functionality being requested: | User Story: | Business reasons that reflect the community or how all customers would benefit: |
7896 | Unify Primo My Library Card display of loans/requests from all institutions in the network (VE/BO) | (VE/BO) | Describe the functionality being requested: | User Story: | Business reasons that reflect the community or how all customers would benefit: |
7897 | Show exact number of results when browsing instead of 20+ (VE) | (VE) | When using Browse Search in Primo VE, if a result has more than 20 results attached to a single subject entry, that subject displays "20+ records" instead of a specific number, which is what Primo shows for any total less than 20. This happens because Primo VE uses the Alma browse functionality, but this is not as informative to users as it should be. |
|
|
7902 | Apply Controlled Vocabulary Service to Primo Browse (VE/BO) | (VE/BO) | Currently, the Controlled Vocabulary Service is only applied to Primo Search. With the CVS, when users search for a term like "heart attack", they see both the list of all results and a message at the top of the results saying "Including 'myocardial infarction'. Just search 'heart attack'". This allows the user to specify which terms are in use, and to narrow them to just the specific term searched for if desired. Primo Browse lacks this service, and only returns precise results. |
|
|
7908 | Initial timeslot offered for Booking requests in Primo should account for transit time between libraries (VE/BO) | (VE/BO) | The initial timeslot offered for Booking requests in Primo should account for transit time between libraries. Here's the present behaviour:
The initial timeslot offered to the patron in Primo should account for the travel time between the two libraries, so when the Durham campus library is selected, the first timeslot should be updated to be 48 hours in the future. | The initial timeslot offered to the patron in Primo should account for the travel time between the two libraries, so when the Durham campus library is selected, the first timeslot should be updated to be 48 hours in the future. | In cases where there is transit time configured between libraries, there is no warning to the patron when the booking can't possibly be filled. The system happily accepts the booking and then our staff have to cancel it and contact the patron. It would be better if the patron was not given options that can't be fulfilled. |
7910 | Hide interloan link if Unpaywall is available (VE/BO) | (VE/BO) | Make it possible to construct a rule in General Electronic Services to hide the Interloan link if Unpaywall access is available (NERS submission recommended by Ex Libris) | Background
Items with DOIs are generally articles (CDI content); and books/book chapters which have a presence in Alma.
Description | This will cause confusion if released into the wild. |
7930 | Local fields should display and be searchable only in that local Primo instance (BO) | (BO) | According to Ex Libris, when a local search field is created in one institution's Alma instance and published to Primo, such as local note 590 or local collection 973, this local search field will be searched across all institutions' Primo instances within a consortium. This current set up poses a problem because results that appear in one institution's Primo may be "false positives" or skew results due to a local field placed by another institution. This also interferes with database categories that use local fields, causing categories to apply to records in unwanted ways. We seek a solution that will reduce confusion and frustration for consortium members by keeping the local fields indexed _and_ displayed in the member Library's instance. Please allow individual institutions, especially for the benefit of those within a consortium, to have the option to create and control local fields that are both displayed and searchable within that institution's Primo instance which will not interfere with another institution's Primo. This request was originally proposed by California State University in 2021 ( ) The request has been slightly modified. Note that this functionality has been addressed for Primo VE with the December 2021 release (Limit Search/Facets of Local Extensions to Local Institution) but it is still needed for Primo BO. |
|
|
7936 | Label distribution per row (VE/BO) | (VE/BO) | In consortial environment there is the option to distibute labels from the Network to the Institutions. At the moment the distribution is only possible per table. In case a table is updated by functionality, the distribution deletes the displayed labels. | Example 1 Adapting labels tables which are partially customized by the IZs | Effort and solution examples: |
7937 | Distribute "configure views" settings via NZ (VE/BO) | (VE/BO) | In general it would be nice to have the possibility to distribute the settings available via Configure views, especially for the General, Brief Record and Full Record services tabs. | Use case 1: | Use Case 1 Requirement: The staff user (discovery admin) should have the possibility to distribute these settings from the NZ to all views of the network, ideally with the option to override/not override the libraries configuration analogue to this option for the labels tables which can be distributed from the NZ to the IZs. |
7938 | Filtering by Institution location facet and Library location facet should include electronic resources (VE/BO) | (VE/BO) | The users expect that with the facets, you would be able to filter electronic resources by library and/or IZ that licensed them. This is currently not the case. When filtering by location, e-resources (incl. external data sources) are not delivered as results. |
|
|
7940 | Shared Digital content settings are inappropriately applied to external resources (NZ/IZ environments). Make these separate configurations (VE/BO) | (VE/BO) | When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. |
|
|
7944 | Enable displaying of additional fields in collections discovery (VE/BO) | (VE/BO) | Currently, in Collections Discovery results pages, only the title field and the material type are shown with the thumbnail. It isn't possible to select other useful fields, e.g. author and year, to be included. This means users might need to click through into the Primo record to get more information. | We have a collection of titles that were written by authors belonging to our institution. At present, it isn't possible to see which titles relate to which authors. |
|
7949 | Ability to make Display Normalization Rules based on Holdings Information (VE) | (VE) | Make it possible to generate normalization/display/custom fields based on information contained within the holdings record, in addition to bibliographic record. | In Primo BO, you were able to write normalization routines based on a record's AVA field. This would allow you to add special facets, etc., or change the display text accordingly, based on certain conditions. This is not so in Primo VE, and you cannot recreate this functionality using existing methods | In Primo BO, we used the AVA field to generate custom floor indicators, based upon an item's location and call number. While this process can be accomplished using 3rd party tools, such as StackMaps, the lack of built-in functionality limits its use. Additionally, since the record is normalized in real time, we could use it to add certain display fields in the Primo record, based on conditions found within the holding record, without having to run a normalization routine on a particular set. This could be useful in the event that we have to close certain locations unexpectedly (or similar) and a note can dynamically be added to every record found in that location, or similar, without having to interact with the record itself in Alma. |
7950 | Enable pinning of specific titles to the top of results pages in Collections Discovery (VE/BO) | (VE/BO) | We would like to be able to pin or highlight particular titles to appear persistently at the top of a collection or sub-collection when navigating through Collections Discovery in Primo. Ideally, the functionality to pin specific titles would appear as part of the title list tab within the Collection Resource Editor screen in Alma, with an option to 'Highlight title' and an additional column in the table to identify which titles have been pinned. |
|
|
7951 | Preview number of titles in collections and sub-collections with thumbnail (VE/BO) | (VE/BO) | In Collections Discovery in Primo, the number of titles in a given collection or sub-collection is shown on the page within the collection or sub-collection - e.g. 'Items (123)' - but is not shown at the level above. For example, it isn't possible to see the number of titles within a particular collection while in the Collections Lobby. | Users would like to know the number of items in a collection or sub-collection before clicking into it. |
|
7953 | Primo full display: create a DOI link when ever a record contains a DOI (VE/BO) | (VE/BO) | Whenever a DOI is displayed in the Primo full display, a link should be automatically generated from it and displayed in the Primo front end (full display) so that the end user can access the publication even if there is no full text access license. Example: the metadata record contains a DOI 10.1080/1941126X.2021.1911452 which is displayed in full display. A hyperlink should be automatically added to this DOI by adding the base url ( ) to the DOI: https://doi.org/10.1080/1941126X.2018.1521110. This enables the end user to directly access the publishers website even if the institution does not have a licence to access for this publication. Primo administrators should be able to active / deaktivate this option via Primo Back Office. | The researcher is enabled to quickly and easily obtain more information about the publication to better decide whether to obtain a publication when the library does not have access. The scientist may be able to download the publication in full text if the publisher has voluntarily made the publication available on its website (open access bronze). The library cannot configure access in these cases because it has no corresponding information about the duration of accessibility of such publications on the publisher's website. |
|
7957 | Option to display resource sharing service in View It (VE/BO) | (VE/BO) | Currently, Primo will only display an option for the site's resource sharing service (document delivery) when there is a Get It. It is reasonable for ideal workflows to not display this service for View It, but there are many situations when a user sees no link because of link resolver failures within Primo or sees a link in Primo but arrives at the source platform to find there is actually an error and no full text content. It is proposed that sites be able to show their resource sharing service in View It, regardless of a link to resource being present or not, by configuration option. This will give the user an access point directly at point-of-need to place a resource sharing request, taking advantage of Primo pre-filling the record metadata into Primo's embedded form or into the site's partner service form. As some sites may wish to adjust when this is available to users, such as to opt out completely, to show only for link resolver failure, or to show the service at all times regardless of resource links being present, the feature must have comprehensive configuration options for all situations to show or hide. See document attached for additional details. | When patrons run into dead ends in attempting to link out to external databases, it would be helpful to also have an option to fill in the Resource Sharing Form with all the data is already in the article record. Currently, if there are links to external resources, there is no Resource Sharing link available. | As matters stand now, we all know that it can be discouraging for patrons and librarians to come across a dead link or even more. Even though many libraries have incorporated opportunities for users to report these problems to the library through Primo functionality or other means, this still involves the patron needing to explain what the problem is and the librarian needing to get back to the patron. In the meantime, the user may well wonder if they could possibly get the article. If there were an option in the "Get It" area to immediately request the article (again, something like what we see in picture B. above), the user could have the satisfaction of not just letting the library know there is a problem, but also making a concrete request for the article, which gives them immediate assurance that they can still get it. The Primo "citation linker" is always an option as well, but this will make requesting an article far more easy, and may also be important to customer satisfaction -- particularly after they encounter links to databases that do not work in some way! |
7971 | Add a resource type for transcripts and audio in CDI (VE/BO) | (VE/BO) | Currently, several items in Primo show labeled as "Text resource." This occurs for things like radio program transcripts, as well as radio program audio files. | Students looking for sources for projects are often surprised when they find the item they are clicking to from Primo is in the style of a transcript, or not textual at all (as is the case for an audio file of a radio program). This can be a frustrating experience. | Users need accurate information from the discovery layer in skimming through results due to the demands of their assignments. |
7980 | Facets related to subjects and authors (VE/BO) | (VE/BO) | Provide the users with the option to view and browse/choose all of the terms (subjects, authors) returned in the search results and which should be available within those facets. At present there is a limitation of entries per facet for local Primo VE records, and a limit for CDI records in both Primo Back Office and Primo VE, which is too restrictive for discovery. A 'View All' link at the bottom of the facets could be added to enable this. Additionally, within the facet 'subjects', the name of the controlled vocabulary should be added within parenthesis at the right hand side of the preferred terms in order to know from which controlled vocabulary (thesaurus) the preferred term comes from. |
|
|
7981 | Export excel file (VE/BO) | (VE/BO) | At present, the excel functionality only allows to save records in one single excel file from the same results list. Users should be given the possibility to add records from different results lists in one single Excel file (without having to pass via the favorites to do so) |
|
|
7982 | Display of fees with the status "transferred" (and ideally also with status "closed") (VE/BO) | (VE/BO) | For Patrons, Primo UI is the only access point to view their library account, therefore it is very important that they can see their fees there transparently. Current implementation of Primo is showing only fines and fees with status active. |
|
|
7986 | Add "Starts With" Functionality to Call Number in the Advanced Search (VE/BO) | (VE/BO) | We'd like to have "starts with" functionality for the call number field in the advanced search in Primo. Currently, "starts with" advanced searches are only supported for titles. |
| It is helpful to patrons to be able to search for an entire call number subclass (e.g., PA) to find everything available in that range without going to the stacks. The availability of "starts with" for titles leads patrons to expect it for other searches, like call number.
|
7987 | Add Ability to Jump to a Specific Page of Search Results (VE/BO) | (VE/BO) | We would like the ability to jump to a specific page added to the page navigation for search results. | Some examples of when this functionality would be helpful:
--Collection development for Faculty to assess all items in a particular subject matter to see where the holes in the collection are for purchasing purposes. |
|