Primo Enhancements - 1st Round
ID | Title | Description |
6515 | "Sort by: Date Newest" to use dates in 260 and 264 fields in addition to 008 (Primo VE) | We request that the 260 and 264 field also be considered when no date is present in the 008, as it is done for the Display Section in Primo. The current functionality only uses the date in the 008 for sorting via "Sort by: Date-newest" in Primo, and the 008 does not contain a date in all of our MARC records. As a result, the "Sort by: Date-newest" option in the Filters does not produce records by date as expected in Primo. |
6745 | We would like users to be able to set preferences such as a preferred citation style and sort order as well as turning off Virtual Shelf if they don't use it. | |
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) | |
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). | |
6712 | Currently if the search expansion with controlled vocabulary feature is switched on, the search expansion is automatically included in the search by default and the user has to click to remove the expanded terms from their search. It would be beneficial to have the ability to have the feature switched on, but with the expansion not included by default and for the user to be able to include the expanded terms if desired. https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37641145-primo-ve-ability-to-search-without-search-expansi | |
6660 | When you test normalization rules for external data sources in Primo VE, you need to upload your test record from your computer EVERY TIME you make a change in the NR. It should be possible to store sample records for easier testing | |
6701 | Sometimes, licenses have confidentiality clauses, so we can't show them in Primo, but right now, it is an all or nothing prospect. It would be great if a checkbox on the record could suppress a confidential license from showing up in Discovery. (Ideas Exchange https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/10017924-ability-to-suppress-licenses-from-discovery) | |
6711 | We would like the ability to report on all search strings, not just Popular and Zero Results. To do so we request that complete search logs be included in Primo Analytics. Search logs would include the search string, when it was searched for, and details of any scopes, tabs, or fields selected that made up the search. See the Idea Exchange idea for the same: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35874370-primo-analytics-ability-to-report-on-all-search | |
5671 | Add "save item" pin to "Share/Save" section in the full display of the record | Currently, when in the full record display, the pin for saving items is displayed in the upper part of the screen. It would be more accessible to the patron if the would be displayed in save section. |
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. | |
6682 | A proximity operator allows a researcher to specify that their search terms are present in records within a specified number of words from each other. Summon already incorporates this feature, performed by enclosing search terms in quotation marks and using tilde and the number distance, for example "yeast bread"~10 finds material where "yeast" and "bread" appear within 10 words of each other. See https://knowledge.exlibrisgroup.com/Summon/Product_Documentation/Searching_in_The_Summon_Service/Search_Features/Summon%3A_Boolean%2C_Phrase%2C_Wildcard_and_Proximity_Searching#proximity Primo’s search algorithm incorporates an out-of-the-box assignment of higher ranking to records where search terms are closer together, but a proximity search operator gives a researcher explicitly more control over precise targeting of their search, which would also help to build greater understanding and confidence that the results will meet their needs and aren’t just from a mysterious “black box”. With CDI coming soon to Primo, along with the massive increase in records, this trust building will be even more important to support researchers with tools to help sift through billions of results. This tool should primarily support PNX and equivalent record metadata (both Primo via Back Office and Primo VE deployment models), but ideally would also incorporate standard existing extensions to remote data where available, including table of contents, abstracts, and full text. See Idea Exchange submission: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19308214-proximity-search-operator-for-fulltext-search-in-p | |
6704 | Add a search results permalink to the results page for Primo NUI | When we do Primo searches for patrons, we often want to be able to send them to a list of results, rather than a specific item. The URL in the address bar can be used for this purpose, but it is very long and contains a complex query, includes internal codes such as scope, tab, and vid, which are meaningless to a user. A jquery customization for the classic UI was created by Western Washington University at https://www.orbiscascade.org/blog/9/?bid=121 However, that customization does not work on the new UI, and requires users to be able to create a SQL database to store redirects, and to store files on a local server. Ideally, search results permalink functionality could be built into Primo's New UI. (Ideas Exchange https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/31138705-add-a-search-results-permalink-to-the-new-ui-resul) |
6653 | Add actionable indication to users for results returned by author pseudonyms | When performing a search query for an author, results are returned also for indexed associated pseudonyms. For example, an author search for J.K. Rowling returns results for the pseudonym Robert Galbraith. However, unlike with Controlled Vocabulary keyword search expansions with a message displayed to the user, the user is given no indication why results are included for author pseudonyms. This enhancement would make author searches behave like Controlled Vocabulary search expansions by providing proper notification, and giving the user the option to exclude the search results. For example, to display a message and hyperlink option of: Including "Robert Galbraith". Just search J.K. Rowling |
6634 | In the Primo back office the Browse section of the PNX supports only author, title, subject and callnumber browsing. We propose that a number of additional browse indexes including series, publisher and barcode are added. 6227 | |
6532 | Add in-line display option for textual holdings and notes (866 a,z) in Get It section | The display of the 866 a (holdings) and z (notes) subfields as separate lines in Primo VE is confusing for users. We request the option to display the 866 subfields a and z in the same line in Primo. See SalesForce Case# 00679649 |
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. | |
6645 | Changing the language in Primo should update the preferred language in Alma | |
6658 | Resource Recommender should disappear after actions are taken on page | |
6723 | In Primo, only the electronic holdings for e-books and e-journals are taken into consideration when determining the availability for a record/article from the central index (PCI/CDI). The libraries also have print/physical holdings of journals that can fulfill the needs of the end-user and that can fill gaps in electronic coverage. If the user searches for an article that the library only has as part of the physical journal holdings, the availability of the article is set to "Not available," and depending on the configuration, the article might not even show up in the results list. This has been addressed in another Idea: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19965871-physical-holdings-should-be-considered-in-determin, which has the status of "Already supported", but it is only supported by Primo VE and does not appear to completely solve the intention of the idea. I ask that Ex Libris provide an option/function in Alma to either upload a file in a specific format (e.g. SFX threshold structure $obj->parsedDate('>=',2000,52,1) && $obj->parsedDate('<=',2007,59,4) for print journal holdings, or some other way to structure the coverage of a print journal. SFX users have this option.. This information must then be added to the Primo holdings file and be used to determine the availability of an article for the central index. This must be supported for all Primo versions and not only Primo VE. Also added to Ideas Exchange: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/39403180-possibillity-to-add-print-journal-holdings-to-prim | |
6633 | Add Show Actions icons to 1) search results selection and 2) to My Favorites | Option to add all the Show Actions icons to display on the search results selection and on My Favorites, or at least some icons such as the print and e-mail icons, instead of just the ... Please see 2 screen captures attached. |
6710 | Add support for microlanguages ISO 639-3 and language codes recognised by Library of Congress | 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 |
6755 | Add writable directive in the third column of the search result set UI element. | in the third column of the search result set (the one within with a class of flex-order-4), there should be a writable directive in that UI element. |
6193 | The filter in the GetIt tab allows users to filter the display of the volumes by year, volume or description. It would be helpful to add a RESET button that will reset the values chosen and display all values available. | |
6649 | The Newspaper search in Primo doesn't provide an advanced search option. There is just a single search box in which to enter keywords to find an article within a newspaper. | |
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). | |
6631 | Allow libraries to configure the Brief Record Display with more flexibility | In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example the attached screenshot). We would like an option that would allow the library to either limit the number of fields to display (for example max. three 7XX fields) or to only display fields based on the content of some subfields (for example: only display 7XX where $$e equals 'editor', 'publishing director ', 'translator', 'Director', 'film director'...). |
6548 | Allow multiple direct-linking templates for vendors in the Templates Mapping Table | For libraries that have multiple subscriptions for a single vendor, e.g. Gale, please allow more than one location ID/template per Primo institution. Currently the table and configuration only allow one. Case Number: 00709468 |
6644 | In Primo VE it is possible to reorder most of the sections in the full record display through the Discovery configuration in Alma, but not the Send To section. This is inconsequent. It should be possible to reorder all the sections in an easy way, without having to use CSS or javascript. | |
6707 | In May 2018, Primo VE was changed to add a mandatory behaviour of automatically activating the Author Facet as an active filter when clicking on an Author hypertext link in a full record. If sites chose to include birth and death dates by $d in their Author search data to assist users in narrowing their query and results, this is also included in the hypertext link and in the facet term, and the query fails. This problem would be resolved if sites could choose to not use the ‘exact facet operator’ feature, as is possible in Primo Back Office. | |
6748 | Enable continuous integration and delivery with an API to automate uploading and deploying of view packages. | |
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. | |
6533 | We would like to have the option to display the BibTex data within the Primo UI without having to download it. This would simplify and expedient the process of moving BibTex text into a bibliography, by allowing for copying and pasting from the Primo page directly, instead of having to run through several steps of downloading and retrieving. | |
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. | |
6657 | For larger libraries, it would be helpful to have a Campus facet, as a superstructure to the Libraries facet (which can be very long). Unfortunately, this cannot currently be created as a local facet in Pimo VE. Alternatively, there coud be an option to have the libraries nested under their campus (though that would mean some tweaking of the facet sort options.) | |
6744 | Change the "starts with" "title" search NOT to use the sort title values | Currently, the "starts with" "title" search uses the sort title only. Since each record can only have 1 sort title, this kind of search will not working when searching variant, alternative or translated titles. The "start with" "title" index should be populated by the search/title (of which there can be multiple). See salesforce case 00791831. |
6694 | Create new facet for either Fulfillment Units or Terms of Use | Create a new facet that can pull information from either Alma's Fulfillment Units or Terms of Use so libraries can display Physical Item Circulation Status to their patrons. This facet section should also include a mapping table so libraries can consolidate their respective Fulfillment Units or Terms of Use into coherent categories. (ie. Circulating, In-House Use Only, Appointment Required, Unavailable, etc.) |
6440 | Create spinner or indicator for GetIt frame to indicate content is loading | 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. |
6708 | In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible. This means, e.g., that A2 is mapped from display/contributor As most reference managers will read A2 as Series Editor, it would be helpful if the display/contributor could be conditioned to map to AU instead. This is just one example - and why the mapping should be customizable. | |
6730 | Customization of the records brief display for Collection Discovery | The brief display of the items records in the Collection Discovery interface contains only the document type and the document title. We propose to add the possibility to customize which fields appear in the brief display of Collection Discovery records as we already can do it for the brief display in the result list. |
6584 | Add ability to identify a preferred record based on format as well as data source (including external data). For format, need the ability to distinguish between online, print, and microform. Currently print and microform are both calculated as Physical and there is no way to prefer print over microform. Further, duplicate fields from dedup-merge record need to be removed. System should normalize data when doing field comparison. Library should be able to configure which local display fields from the non-preferred record will be retained. - Use case: Library participates in a shared print collection with outside institutions. Library wishes to load external data for this shared print collection into Primo, and dedupe with local data to prevent redundant search results for users, as well as redundant search results in a FRBR cluster. The library wants to always prefer its own print record. - Use case: Library uses Primo as discovery interface for data from Alma and other external systems (archive system, digital repository), but always wants the Alma record to be the preferred record (if available). - Use case: Library has separate records in Alma for print and microform. When these are for the same publication, they want to dedupe the records in Primo and prefer the print record. - Use case: The system does not normalize the data before comparing for likeness, so you end up with duplicate elements where the only difference is punctuation or capitalization, e.g.: <lds34>Everyman</lds34> <lds34>Everyman.</lds34> In other cases, the data is only slightly different, but the library would not wish to retain both fields, e.g.: <lds14>By A. F. Sperry.</lds14> <lds14>by A.F. Sperry.</lds14> | |
5675 | We would like the label indicating the type of sort in the list of loans to be displayed upon the display of the screen. Currently there is no indication on what kind of sort is used to display the list. Preferably, the default sort and label of the 'sort by' column would be "Sort by: Due date - earliest to latest" . | |
6725 | Determine source for Autocomplete suggestions in a blended scope | 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. However, the suggestions from the central index are currently determined by the scope of the view. In blended scopes the suggestions are from both local records and the central index, which can be less useful for the user due to incorporating suggestions from non-activated central index collections. We would like an option in the scope definitions in Primo to decide the source of suggestions for blended scopes to only local records. Meaning that we could decide that we would like to get only the suggestions from the local index and not from the central index in blended scopes. Also added to Idea Exchange: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/39403210-determine-source-for-autocomplete-suggestions-in-a |
6642 | Allow patrons to add a digital library card to their mobile device (i.e. Apple Wallet or Android equivalent) after signing into their Primo account. The digital library card would display: 1. Configurable library logo. 2. Patron first and last name or preferred first and last name. 3. Expiry date from Alma patron record (institutions could enable or disable this field). 4. Barcode (institutions could determine which identifier from the Alma patron record would generate barcode based on user group). If possible, the digital library card would automatically update if the user record was modified in Alma. See attachment for possible example. | |
6721 | For user experience, it would be great to see digitisation history in the My Library Record. | |
5678 | Display 3 items from the hidden menu (the three dots) in the saved records screen | Currently the three dots menu in the Saved Records screen is enabled (and highlighted) only after choosing items from the list. Even then the patron cannot know what actions are available for him through this icon. We would like to display 3 available actions and have the rest hidden under the 3 dots icon (as is for the brief display) |
5679 | Display chosen pre-filters as search limits in the facet column | Currently, when using pre-filters, there is no indication to that, except in the search boxes themselves. It would be very useful and clear to the patron what filters he has used for this search if these filters would be displayed in the facets column, used to display this kind of information (i.e. limits applied to the search). |
6196 | Display multi-lingual values in facets in a consistent order | Currently, same values in different languages in multi-lingual facets (topic, author) appear randomly. We suggest to create a consistent language order independent of the sort by_size configuration option, so that the values in these facets will be displayed by the determined order. For example, if the order will be: Latin, Hebrew, Arabic, Cyrillic - the values will always be displayed by this same language order. See example image provided for the following search: https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,gibran%20kahlil&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=en_US&offset=0 We are suggesting that for the facets set by size in the View, the same value in all languages will be grouped together and displayed one after the other in a consistent order of languages, for example: • Hebrew heading 1 (100) • Arabic heading 1 (100) • Latin heading 1 (100) • Cyrillic heading 1 (100) • Hebrew heading 2 (100) • Arabic heading 2 (100) • Latin heading 2 (100) • Cyrillic heading 2 (100) • Hebrew heading 3 (95) • Arabic heading 3 (95) • Latin heading 3 (95) • Cyrillic heading 3 (95) • Hebrew heading 4 (87) • Arabic heading 4 (87) • Latin heading 4 (87) • Cyrillic heading 4 (87) |
6690 | Display Summary Holdings in full display before clicking the each locations. (Primo VE) | We would like to display the summary holdings of physical location to first "get it" viewing in full display, before clicking the each locations. Also, we'd like to display not only holdings tag 866 but also automatic coverage. Our patrons needs to find the holding coverage quickly for selecting locations from the multiple locations and libraries.There is similar ideas in idea exchange: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35043796-summary-holdings-display-primo-ve |
6696 | Instead of giving a "No Records found message," when a DOI is searched for which the Library does not have access, could Primo query CrossRef or another service to extract relevant details from the DOI (such as title, author, etc.) to provide better search alternatives or to fulfill a ILL request? | |
6638 | Email alerts for failed pipes / indexing in Primo Back Office | Primo should send an email alert when a) a pipe fails, or b) some records in an otherwise successful pipe run failed during harvesting or normalization, or c) when indexing / hotswapping fails. Because there is no alert, many days might pass before we realize there is a problem. When a pipe fails the normal schedule does not resume, meaning no data updates get made to Primo until we find out there has been a failure. No new/updated records are discoverable by our users once a pipe fails. Single records that failed during harvesting or normalization will probably never make it into Primo without intervention. It is unfeasible to expect customers to go into the Back Office every day to check for failures. Example: pipe fails on Sunday. On Thursday, a staff member reports that they created a high demand item on Monday in Alma for course reserves and they still don't see it in Primo and the professor and students are angry. The Back Office shows that the pipe failed on Sunday or that all Sunday's pipes completed successfully but there was no alert for a pipe failure or errors in a completed successfully pipe, and no new/updated records have been processed since then. We have to terminate the pipe and re-execute to have the backlog processed. |
6719 | You can email pinned records to a colleague or student but can't email a saved search. This feature to be able to email a saved search would be handy while helping a student. | |
6753 | Embedded player for JSON manifest for universal IIIF viewer player (to support external DAMs). | Embedded player for JSON manifest for universal IIIF viewer player (to support external DAMs). The universal IIIF viewer (https://universalviewer.io/) uses a json-based manifest to display zoomable images and multiple page documents. We would like this functionality to create a new instance of the IIIF viewer if a URL exists to a properly created IIIF manifest in the link section of the PNX (or whatever its called in Primo VE) for a newly created value such as link:iiif. We believe this would significantly help the use of primo with other DAMs other than Alma-D. Please see https://ddmal.music.mcgill.ca/IIIF-AV-player/ for IIIF-based example for video. Similar to player for images, a json-based manifest would be viewable if manifest link existed in item data within fullview display. Ideally, this could also be used for activated alexander street press and/or kanopy/digitalcampus collections. |
6683 | Library users expect ‘shopping cart’ functionality for transactions in Primo. Currently for any type of request the user has to submit requests one at a time. For researchers, especially those undertaking systematic reviews, this is extremely time-consuming and tedious. Institutions should be able to configure: -which user groups/and or job categories are enabled to submit batch requests -the maximum size of the shopping cart per user group/job category/request type eg. Researchers get a bigger cart than undergraduates. -whether to display this option in each Primo view -copyright declaration for batches of resource sharing requests The number of simultaneous requests of each type should consider both the maximum size of shopping cart and the number of current requests of the user. If the user already has maximum concurrent requests then a message should be displayed to the user that they cannot submit more requests yet. If the user has capacity for N requests to be submitted then that should be conveyed to them when submitting requests. | |
6717 | Expand Primo VE functionality to support browse searching of Moys call numbers | Expand Primo VE functionality to support Moys call number browse search which is currently unavailability in Primo VE. That functionality is available in Primo BO NUI and is supported in Alma. |
6706 | As a request from our institution (which uses Primo VE), Primo currently displays and links authority strings for name/titles from the 100/240 and 700 fields. Since this feature has been proven successful with our user base, we would like to expand this capability to the 110/240 and 111/240 combinations as well as to the 130, 700, 710, 711, and 730 fields. We feel this is an essential feature for users seeking to navigate the catalog in those subject areas that rely heavily on canonical literatures, such as divinity, classics, fiction, and music, and for any work presented in translation. Source 700, 710, and 711 (only if $$t exists and 2nd indicator anything except 2): Display $$i first – if present Display 700 all remaining subfields except $$x and numeric subfields (have a space between elements) Link all of 700 string except $$i and $$f Source 730 (only if 2nd indicator anything except 2): Display $$i first – if present Display 730 all remaining subfields except $$x and numeric subfields (have a space between elements) Link all of 730 string except $$i and $$f For INCLUDES: Source 100/240, 110/240 Take all subfields of 100 except $$e and numeric Take 240 with all subfields (except numeric) and add to end of string (have a space between elements) Link should contain entire string except $$f Source 111/240 (can be grouped with 100/240 “Includes:” if already present) Take all subfields of 111 except $$j and numeric Take 240 with all subfields (except numeric) and add to end of string (have a space between elements) Link should contain entire string except $$f Source 130 (can be grouped with 100/240 “Includes:” if already present) Take all subfields of 130 except numeric Link should contain entire string except $$f Source 700, 710, 711 (only if $$t exists and 2nd indicator 2) (can be grouped with 100/240 “Includes:” if already present) Display 700 with all remaining subfields except $$i, $$x and numeric (have a space between elements) Link should contain entire string except $$i and $$f Source 730 (only if 2nd indicator 2) (can be grouped with 100/240 “Includes:” if already present) Display 730 with all remaining subfields except $$i, $$x and numeric (have a space between elements) Link all of 730 string except $$f | |
6722 | There is no way to create queries in Analytics for retrieving Primo Permalink. It would be beneficial when sharing the search results with patrons. This is the use case: Our library generates new e-resources or new ebooks for promotion every week. In promotion materials, we provides Primo permalink for users to access a record full display as well. It would be a great help if there is a function for exporting/extracting the permalink from Primo. | |
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. | |
6728 | Favorites/eshelf should be able to be sorted by publication date or call number | |
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. | |
6583 |
| |
6750 | FRBR Profile - we would like a FRBR profile for our Primo view that only groups books. Audio-visual materials or musical materials should not be grouped. The views wizard choice of which resource types to FRBR would override any normalisation rule logic. | |
6756 | full integration of syndetics content - ideally, syndetics info (such as awards or TOCs) should not just be added to the display of titles, but should also be indexed as part of the search record, particularly chapter titles, chapter authors and chapter co-authors. ideally, orchidID information would be included with this syndetic data. *FROM 6732* Syndetics Solutions Indexed Content Enrichment (ICE) should be integrated into Primo as it is in Summon to aid the discovery of monographs. Syndetics Unbound is insufficient as it is a JavaScript layer that does not aid in the discovery process – it simply adds load time to the user’s experience, which is undesirable. Syndetics ICE has some great features to aid in book discovery that will enhance our institution’s metadata: · Discovery access to tables of contents, annotations and fiction profiles, as well as supplemental options such as Title Link and Customized Fiction Connection · Works to give patrons an easier and more productive search experience in the library · Eases the visibility of a library's holdings and brings greater relevancy to search results by helping patrons find the items that they would have otherwise missed with traditional searches This request originally appeared on https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/11034849-full-integration-of-syndetics-enrichment-content | |
6557 | Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount. | |
6699 | Currently, the user is not able to browse a library's entire holdings using the Browse Search functionality for Subject. Library of Congress Subject Headings (LCSH) and LCNAMES for 651 should be combined, so that subject headings that can be added to bibliographic records in the metadata editor by library staff can also be browsed by users within a single "Browse Subject" list in Primo. | |
6734 | Currently, for patrons who belong to a consortia, the Primo My Account page displays all institutions that a library user has ever borrowed material from, regardless of whether or not they have active loans with that institution. We suggest a few changes to the Primo My Account page for a better user experience. First, the default view for the patrons should show all checked out materials in one view so that patrons aren’t required to select each institution separately to see checked out materials. Second, next to each institution listed in the My Account page show the number of items checked out in parentheses. Finally, if a patron has no items checked out or fines from a particular school, then hide that school from the My Account page listing. As an alternative to the recommended default view, the user should also have the ability to choose their view and filter by clicking on any library where they have active loans and only seeing materials from that library. To return to the default view, a “See All” option should be included as well. And with this view showing all loans, it would make sense to have the “renew all items” link apply to loans from all institutions. | |
6757 | improve peer review indicators - Move 'peer-reviewed' out of the availability facet to its own facet group and apply peer-reviewed indicator to the article-level instead of the journal title (which is usually derived from Ulrichsweb). | |
6709 | Improve the appearance of the record when exported to print. Add all holdings information to the printed version. Include the 866 holdings field. The current out-of-the-box print record is basic, cannot be changed and lacks all necessary information. | |
6759 | include SMS option out of the box for sending shortlinks to patrons. | include SMS option out of the box for sending shortlinks to patrons. |
6652 | Include the 776 field in ISBN matching when deduping books for Primo VE | Improve deduping of books in Primo VE by including the 776 field in ISBN matching. Currently, the algorithm only checks the 020 field for ISBN. In many cases, an electronic version of a book has the print ISBN in the 776 field, which would allow for a match of the electronic 776 to the print 020. The February 2019 VE release included an improvement that allowed the 776 field to be used when matching journal ISSNs, but it is still not being used when matching book ISBNs. |
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. | |
6697 | Allow user to apply a label while adding a single record to their favorites by clicking on the pin icon in the brief record display. This is to achieve consistency of the behavior of the "pin" icon regardless of where/when you select it. | |
6726 | Is it possible to view citations from reading lists that are in the third party repository (e.g. Fedora Commons, ArchivesSpace), but not in Alma? | |
6681 | Currently, collection discovery is not localized for institutions in a consortium. For example, collections from institution A show up in institution B's Primo instance. This is confusing and misleading. | |
6700 | Make users more aware of results found in other search profiles / scopes / slots / tabs | In most Primo instances, users can search in different search profiles, scopes, slots, and tabs, depending on deployment model and configuration, for example Library Catalogue, PCI, Everything. However, our users do not switch a lot between the different options. The majority performs the whole session in the same search option. In order to make the users more aware of the different options and the different content available, we suggest implementing UI features that emphasise the other content by 1. on top of the results list, the number of results in every defined option should be displayed. The displayed information should be a link, so that the users can easily switch to the result list in another option. And 2. another facet labeled “Other Search Options” and in it, include the individual options and the number of results found using the same search performed originally. This would enhance our ability to reach users by providing multiple means to get the results they desire. (Previous NERS Request #6632) |
6680 | Missing Form Label for Searchbox & Missing Search Button Label |
|
6691 | For now, the sort order of loans in My library Card is sorted by "Due date- newest" as default. We would like to configure the sort order to "Due date - oldest" as default. Unfortunately we can not set the default orders in PrimoVE. Our patrons need to set the sort order by themselves. Patrons who have 100+ active loans demand to see the old loans for returning materials in near future. They want to see them as soon as possible, however sometimes they can not find even the sort option. In addition, it takes sometime to change display for 100+ active loans. | |
6671 | My Library card: prevent external users from editing Personal Details | Today it is only possible to allow/disallow editing the Personal Details in Primo for all users, regardless of the account type. As the functionality is different for external and internal users there is a need for differentiation between the account types. As external users get their personal details from the SIS feed they should not be able to edit the information. It only creates confusion. I should be possible to turn the edit function off for external users and keep it for internal users. |
6651 | Open records for which direct linking is disabled in the same browser tab rather than a new tab | When direct linking is enabled, users can access full text by clicking on an item's availability statement right from the brief results page. However, customers may choose to disable direct linking under certain conditions (the presence of an authentication note) or for certain resource types (journals). Clicking on the availability statement for resources that have been excluded from direct linking opens the detailed record in a new window. This behavior is often confusing to users and makes it more difficult to return to search results. This enhancement would allow these records to open in the same window. Ideally, clicking on the availability statement action should mimic the same behavior that occurs when direct linking is turned off (full record displayed in an overlay with focus placed on the "Get it" section). |
6716 | Option to create additional links for records from external data sources in Primo VE | At time, in Primo VE, it is only possible to create a link to the resource and a link to the thumbnail in the Import Profile for external data sources. In Primo with a BO, however, it is possible to create nearly as many links in the PNX links section as you like. We use these links a lot for the records of our many different data sources, e.g. create links to an abstract or tables of content, links to related titles, and many mores. These links help to enrich metadata and are user friendly. Therefore, we suggest that in Primo VE, there should be an option to define at least three additional links per external data source. As in Primo with a BO, the link URL should be taken either from a template or from a source field. Customers should be able to freely determine and translate the names of the links. |
6751 | SuperTabs - we would like to have the option of moving the resourceType facet group from the facets tab to a new tab interface above the search results set. This would allow a similar user experience to google, bing and other mixed content-based search engines. We would ask that an 'All' tab be the default result set, but that highest to lowest or alphabetical faceting could be followed. Ideally, we would like news articles to be under a "news" tab. We would ask that facet counts be included to the side or under the title. The top 5 resource types could be included with a descending "more..." option with other resource types below. | |
6741 | Optionally ignore call number prefix (subfield k) when indexing for LC Call Number Browse | Reconfigure Primo's browse search index to ignore (but still display) the call number prefix (holdings 852 $k) when generating the LC Call Number index. This should be an optional configuration. |
6731 | Possibility to add a remote search scope to Primo VE in Primo on Back Office and vice versa | It now possible to add a remote search scope in Primo VE to another Primo VE, as well as in Primo Classic to another Primo Classic. We would like to add the possiblity to add cross-product remote search scope, in Primo Classic to Primo VE and vice versa. |
6729 | Prevent Autocomplete suggestions from non-activated sources in PCI / CDI | 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 that the suggestions are based only on activated sources in PCI / 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 |
6639 | Primo VE : possibility to search /filter by code or label within a label table | In Primo VE, it is currently possible to search for labels and code, but this just allows you to search for, and access to the good label table. Once inside a given table, it is only possible to filter by label language. We would like to add the possibility to search or filter within the tab by code or label, such as what is currently possible on Primo BO, where you can search and display only the line you are looking for, without scrolling along the whole table or using a Ctrl+F. This would be much more effective for administrators. |
6714 | It would be useful to be able to include multiple facets for both external data source and library at the same time to filter/pre-filter searches in Primo VE. At the moment, whilst some facets such as author, and resource type can be used across local and external record results, it is not possible to include a mix of both local and external records using both external data source and library filters; you can only use one or the other (e.g. including library excludes external records and vice versa). | |
6656 | Primo VE: Calculated Availability field should be configuratble | The Calculated Availability text is composed of Availability status + Library + location + call number . We want to be able to configure what elements should display based on their value. For instance, we only want to display call numbers for items that are on open shelves (as determined by library and/or location value). For items in closed stacks, the call number is irrelevant to the users and only serves to clutter up the interface. |
6655 | With Primo VE, you can add external names for Locations, but not for Libraries, This means that Libraries will display the same name to end users, as it does to staff users in Alma. The same option as for Location should be available for Libraries too. | |
6692 | Primo VE: need for an option to Show All Items from a location | An option to show All items from a location should be available in Primo VE. Currently if you want to display all items from a location, you have to use the 'Show More Items' button several times which can be very excruciating while displaying newspaper's items. |
6688 | Provide option to collapse the Details area of the full record display | We would like to be able to collapse the Details area of the full record display by default in order to reduce clutter. This ability would be configurable ie libraries could choose whether to hide or show by default the Details information. If configured, we would like to see the heading 'Details' beside a chevron or similar icon that indicates information is hidden. When the user clicks on this icon, the full bibliographic details will appear. |
6695 | Add a tool for targeted adjustment of relevancy for a specific title by Record ID, with choice of increase or decrease of ranking, against specific title/s by Record IDs, to rank one above another. This enhancement would allow sites who have chosen not to use Dedup and FRBR to rank newer editions of materials above older editions of the same title, or force certain print titles above their electronic counterparts (or vice versa), without making the settings global in scope or setting up many complex normalization rules. | |
6715 | Request for a template to generate short permalinks using a fixed code | n 2019, the function to create short permalinks for Primo records became available. Part of the new short permalink structure includes a variable key, changeable by factors such as view, scope, and data source, for example: https://www.librarysearch.manchester.ac.uk/permalink/44MAN_INST/8pfhc8/alma992978604618201631 https://www.librarysearch.manchester.ac.uk/permalink/44MAN_INST/16n6ivq/alma992978604618201631 Primo Back Office template: <Primo Domain>/permalink/<type>/<key>/<record_ID> Primo VE template: <Primo Domain>/permalink/<institution_code>/<key>/<record_ID> The variable key has introduced timeconsuming workflows for permalinks, as the key is not known in advance, so requires that each resource be checked manually in Primo, and the permalink copied and pasted one by one. This affect individuals, such as where library staff provide a personalised service to academics and students in sharing updates of resources recently purchased to support their teaching and learning. It also affects system management bulk processes, such as making impossible automated updating by spreadsheet in third-party products. This request asks that a fixed key is used for the creation of the shorter permalinks, instead of a variable key. |
6674 | Currently, the Search History tab on the My Favorites page contains only the queries that have taken place during a browser session. Search History is cleared when a Primo session ends and/or the user is logged out due to inactivity. It would be extremely useful if Primo automatically saved the search history of a signed-in user when the user logged out or the session timed out. When the user logs back into Primo they could navigate to the Search History page to find their last searches were retained, and add them to their saved searches. The search history retention could be set to a specific time period (e.g., seven days) or a number of queries (e.g., the last 100). This setting should be opt-in for institutions and also opt-in/out for users. | |
6705 | We have users (faculty members) who would like to be able to search within their list of currently checked out items. At present, the only options are (1) export the list of loans to BibTeX or RIS and search them in another program, or (2) sort by checkout date or title. When faculty have 400 items checked out, neither of these options is feasible. They would like a search box option within their account to search across all the items they have checked out. (Ideas Exchange https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38738326-search-loans-within-user-account) | |
6724 | If there is scheduled Primo maintenance or a major outage, patron login will be disrupted. Patrons does not know service disruption is caused by such maintenance, unless we post a message to our website or Primo view landing page manually. Ideally, auto announcement could be setup in Primo New UI. | |
6672 | Show correct holdings information for FRBR-grouped books outside of IZ | An institution owns a specific edition of a book, ex:https://bibsys-almaprimo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=BIBSYS_ILS71566408110002201&context=L&vid=SSHF&search_scope=default_scope&isFrbr=true&tab=alle_bibliotek&lang=no_NO When extending the search scope to other libraries, they may find other editions of the book, which they don’t own (https://bibsys-almaprimo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=BIBSYS_ILS71566408110002201&context=L&vid=SSHF&search_scope=blended_scope&isFrbr=true&tab=alle_bibliotek&lang=no_NO ). The original/owned book's barcode is shown for the other edition(s) as well. This is unfortunate as it is quite confusing (contradictory messages, give the impression the library owns resources it doesn’t), and can lead the user to order the wrong book. The availability status is correct but the holdings information is not. The ISBN should be used here to prevent tis from happening, instead of the holdings being based on the title only. According to Ex Libris (#00628723), this is by design: " this issue is indeed connected to the FRBR-grouping of the two records - because they are FRBR-grouped, you can see the items for both records in each of them". The only solution is to disable the FRBR-grouping. This is not an option for us to have it disabled in the local index, so we are hereby suggesting that another solution be found, preventing the problem described here, while havig FRBR-grouping enabled. |
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. | |
6713 | Following the introduction of support for FRBR and dedup for external records in the February Primo VE release, it should be possible to apply suppress rules for FRBR and dedup to external data, in the same way you currently can for local records. | |
6752 | At the moment, the check boxes to select multiple facets only appear when you hover on a facet. Ticking one then allows all the others to be ticked and applied together but it would be much better if the check boxes showed by default. Hiding them leads to low engagement for the product's filtering features. | |
6553 | (From Idea Exchange Post): The functionality introduced in the April 2019 release only allows you to specify ONE field in the source MARC record that contains the resource type that you want to map to the local resource type. Primo VE should to be able to determine the resource type from combinations of data in MORE THAN ONE of the fields in the MARC record; i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field. | |
6195 | It would be very useful if upon clicking on the unpin icon in the favorites screen, Primo will display a warning message stating that the user is about to delete the marked record/s. Currently, clicking willingly or inadvertently on the unpin icon will immediately and irreversibly delete the record/s. |