| RequestTitle | Module | Description |
| Ability to change facet sort in the UI(6414) | Primo Software | 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 the UI, since the chosen “default” sort isn’t best for all situations. |
| Ability to configure Resource Recommender items at View level(6316) | Primo Software | Currently Resource Recommender items can only be configured at the Primo institution level. It is desirable that items be configurable at the view level. UNSW has setup the Resource Recommender for our subject guides and our most popular databases. Our Sydney and Canberra campuses maintain separate subject guides. There are separate Sydney and Canberra views but both sets of subject guides display in both views due to the institution level configuration. |
| Ability to copy multiple citations to the clipboard(6198) | Primo Software | If you do a search in Primo and pin multiple items, you can then go to your favorites list, select multiple items from the list, and click the ellipses at the top of the list to get push-to actions. These actions do not include the CITATION option (indicated by quotation mark) that's available when you select only a single resource and click the ellipses next to that. We would like the ability to select multiple resources and use the CITATION option for them all, rather than copying each to the clipboard individually. |
| Add "save item" pin to "Share/Save" section in the full display of the record(5671) | Primo Software | 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. |
| Add additional browse indexes(6227) | Primo Software | In the Primo back office (Primo classic), the Browse section of the PNX supports only author, title, subject and callnumber browsing. We propose that a good number of additional browse indexes including series, publisher and barcode are added. |
| Add Show Actions icons to My Favorites(5821) | Primo Software | Option to add all the Show Actions icons to display on My Favorites, or at least some icons such as the print and e-mail icons, instead of just the ... Please see screen capture attached. |
| Adding reset button to the volume filter in the GetIt tab(6193) | Primo Software | 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. |
| Allow Primo Proxy Login(4671) | Primo Software | Currently patrons can only request materials via Primo for their own account. We would like the patron who is assigned as a proxy for another user to be able to request materials on behalf of the person for whom the patron is a proxy. Just like fulfillment staff in Alma can check out an item to a patron and indicate that it is for his or her proxy relationship, so we would like the patron him/herself to be able to do that in Primo. |
| Automatic sync of library codes with scopes and static facets(5883) | Primo Software | In the Primo classic back office, the Library Codes on the Institution page are currently automatically copied to the Library Names code table and the ILS Library Codes mapping table, which is great. We would like to have an option to automatically sync these library codes also with the Scopes and Search Scopes (used for searching, and Location drop-down lists) and Static Library facets mapping table, in order to eliminate the need for manually updating all library codes in the scopes and static facets. |
| Dedup and FRBR cluster monitoring(6206) | Primo Software | Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that add up to a score for each cluster. The Dedup Tools in Primo and Primo VE are helpful when a "bad cluster" is brought to our attention by a customer, but we should not have to wait for this to happen if the cluster size, or random sampling, can bring problems to light. Regular Primo customers need better tools that will provide a more usable output in modern spreadsheet or document formats, and VE customers need similar tools to sample and monitor clusters. If this can be part of Analytics that would be fine, otherwise a separate set of tools is needed. |
| Deduplication of same title/same ISBN/different editions(6229) | Primo Software | From time to time we come across the same ISBN used for different editions of the same title, particularly in the case of law books. Instead of displaying as multiple versions in Primo, these editions are combined into one record and no one would know about the older edition(s) if they don't click Display source record. A variation on the issue are two records with the same title/different ISBN, one being the English translation and one the Xhosa translation. The ideal would be if these two records appear as multiple versions instead of being merged into one record because the Xhosa record gets preference and would be confusing to those interested in the English version (and vice versa). |
| Display chosen pre-filters as search limits in the facet column(5679) | Primo Software | 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). |
| Display multi-lingual values in facets in a consistent order(6196) | Primo Software | 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) |
| e-shelf sorting by publication date or call number(6291) | Primo Software | patron should be able to sort their e-shelf (favorites/pinned) records by publication date or call number |
| Editable table for PNX Languages(5952) | Primo Software | For "Chinese" and "English" records, the normalization rules are fine to convert the dc:language Chinese and dc:language English to PNX display/language and facets/language "chi" and "eng" respectively. But for dc:language Cantonese and dc:language Chinese (Simplified) PNX display/language is fine but not PNX facets/language. It would be great if ExL could open a mapping table for the library to customize the language mapping. |
| Embed Altmetrics Data on Main (Brief Record) Results Display Without Additional Charge to Customers(6428) | Primo Software | In Summon, Altmetrics data is embedded into the main (brief record) results display without any addition charges to customers. Users became accustomed to this feature in Summon, and we would like to be able to provide it again using Primo. |
| Embedding Media playback in Primo/PrimoVE(6149) | Primo Software | When available the ability to embed media playback in Primo would be ideal. This should include embedding of video, audio, high-resolution images, etc. through the means of an inline iframe, modal/dialog, pop-out, etc. For images the availability of a high-resolution image viewer that support the IIIF Image and Presentation API's would create a low bar of entry for institutions that already have a IIIF server available. |
| Export search results to Excel/csv(6190) | Primo Software | When a user gets several hundred search results, they need to be able to download a list of the entire set of results. This is a feature that faculty and research assistants routinely used in our Aleph OPAC, and a tool they use in research databases. They see this as a drawback of doing research in Primo. There is no way in Primo to capture an entire set of search results and do anything with it, such as export. The closest thing they can do is to take a series of onerous steps: 1) load 10 search results at a time, 2) individually "pin" each one, then do the same for the next 10, etc. 3) go to e-shelf and tag them all, 4) export items to a new library in Zotero, 5) export to CSV from Zotero. The ability to export a set of search results was a feature in the Aleph OPAC. There is no feature parity in Primo. Users have noted the lack of this feature. |
| Fix indexing of words with hyphens (e.g. hand-book, etc.)(4457) | Primo Software | 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. |
| For related holdings, show related bib title in Get It summary holdings(5947) | Primo Software | Previous title: Display 774 related title in holdings summary We would like the option to include the title of a related item in the holdings summary screen. Currently, a user sees "Related Item" below the Library, Location, and Call Number Details. Users have to click the Library/Location/Call Number link to see the related title. |
| Hide Resource Sharing request option in Primo for Alma's Network Zone-managed e-resources(6141) | Primo Software | We would like the ability to hide Alma's Resource Sharing request option in Primo for e-resources managed in the Network Zone, unless there’s also a physical copy of the item at another library in our consortium. |
| Improve NUI user actions on mobile devices.(6290) | Primo Software | Actions such as navigating and using the 'Send to' menu, Expanding and collapsing OvP blocks, and applying filters are unreliable and slow on mobile devices. Design improvements that would allow mobile devices to be a viable platform for catalog searching would be desirable. |
| Limit call number browse by location(6294) | Primo Software | Users should be able to limit by location when browsing by call number. Users want to be able to browse materials in a closed stack or off-site location 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. |
| Make it possible to override Start Harvest date for Delete and ReLoad pipes(6184) | Primo Software | Each time a Delete Data Source and ReLoad pipe is run, the "Stop harvesting files/records from" value in the pipe setup changes to the date the pipe was run. This means that if such a pipe is scheduled to run at regular intervals then the pipe must be edited each time to ensure that the earliest records are harvested. We would like to see an option to either set the start harvest files date to a static date, or to suppress the start harvesting feature entirely for this sort of pipe. |
| Make it possible to remove the 'until' date in OAI request for all pipes(6186) | Primo Software | Each time a pipe harvesting using OAI method is run, the OAI request sets the 'until' parameter to the time the pipe is run. Here is an example of such OAI request: https://ourjournals.ac.nz/index.php/LPR/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2018-11-05T01:44:31Z&until=2018-12-01T22:40:07Z When the target OAI feeds contain records that do not have a date stamp, it will be automatically filled with the date/time the record is accessed by the OAI harvester. This means that all these records without a date stamp will never be harvested into Primo as they will be always have a later date stamp than the 'until' parameter. We would like to see an option to either set the until parameter or it is removed from OAI requests for all pipes. This will give more flexibility to enable records being harvested into Primo using OAI method. |
| NUI: Copy & Paste citation in richtext format(6118) | Primo Software | The "citation" tool copies citations to the clipboard in plain text format. Could Primo be modified to allow citations to be copied in rich-text format, in order to preserve the formatting in the citation? |
| Primo VE: Need for new ‘Discovery Manager’ roles(6192) | Primo Software | Create Discovery Manager roles and give customers the possibility to assign Discovery roles to colleagues who are in charge of specific content updates in the front end (notably Tag management, Resource Recommender management, Primo Central Index activations/deactivations) and who are not necessarily Primo administrators. For more flexibility and granularity, different roles (or parameters to add?) should be created. For example, a staff user in charge of Resource Recommender management should not necessarily have access to PCI activations. |
| Remove Resource Recommender once the patron uses facets(5680) | Primo Software | The Resource Recommender is displayed in accordance to the search terms. This is displayed as long as the patron is using the results list, and continues to be displayed even after narrowing the results list with facets. We would like the resource recommender to be displayed only once, after the initial search, after which it should no longer appear, until a new search is performed. |
| RESTful API to automatically upload and deploy view packages(6289) | Primo Software | Currently, changes to customized view packages need to be manually uploaded via the back office. Such an API would facilitate use of automated continuous integration practices. When developers make changes to their frontend view package source code, they are required manually upload compiled assets via the back office graphical user interface, followed by manually triggering a deployment phase. This creates administrative friction between a developer committing changes to their source code, and deploying the resulting assets to a development or production server. This increased administrative overhead reduces developer efficiency, and, equally importantly, disincentives rapid iteration to deployed products. In order to allow for automated deployments, a user must be able to be authenticated, read assets, upload assets, and trigger deploys through an API. The web's typical interface for this kind of interaction is a RESTful API allowing users to perform GET (read), PUT/POST/PATCH (write or update), and DELETE (delete) functions through a documented URL scheme. In the context of Primo frontend packages, this would imply building HTTP interfaces for users to download their current package for a specific view (GET), to upload compiled assets for a specific, known view (POST), to delete the assets for a view (DELETE), and to trigger a deploy (GET, or POST if requiring specific parameters). For security, users can be authenticated using username/password authorization headers, or through the use of regenerable security tokens. |
| Set automatically the cursor in the search box(6341) | Primo Software | A feature that many patrons would like to see in the Primo new UI is to have the cursor already in the search box when they open the page. The user would be able to type directly their query and not have to click first in the search box. In the Primo classic UI, the cursor was already in the search box. |
| Sort order of libraries/locations(6228) | Primo Software | We have an issue with the way our libraries/locations within a campus and IP range are sorted, especially which librarylocation is displayed first (on the brief results view). When there are titles held in multiple libraries and locations, enable the ability to determine which library and locations will appear first, second, third, etc. in the record. |
| Sort purchase requests in Primo, by newest(6112) | Primo Software | "In 'My Account' the Requests section is lacking the option to sort according to the request date. Please enhance the sort options of the My Account Request section to feature parity with the Loans section, enabling the patron to sort according to "request date - newest", "request date - oldest" or "title". |
| Sticky facets by default(6125) | Primo Software | Create a configuration option (or force by default) Primo's facets be sticky by default when a user selects a facet in their search. Users do not understand why searching a modified keyword continues to remove the facets selects and are getting very frustrated when they have to remember and reselect all the facets they previously used. It's not common for users to perform a single search and then perform a completely different search - they are usually modifying keywords to get the results they need for research. Once a new search is initiated, the sticky facets should be removed, but once a user selects facets again, they should be sticky. |
| Support custom labels for featured results(6205) | Primo Software | Currently Primo (New UI) does not support custom labels for Featured Results. Please add support for customizing Featured Results Labels in the New UI. See case 00582091 for more information. |
| Tool to Force the Relevancy Ranking Hierarchy for a Specific Set of PNX Values (RecordIDs)(6369) | Primo Software | e would like to see some sort of tool where we can input 2 or more PNX records that will prioritize the relevancy ranking of those records when they appear in a common result set. This request would create a mechanism through which titles with multiple editions can be forced to sort chronologically in a results set, regardless of FRBR and/or user-selected sorting in the Primo interface. |
| warning message when unpinning a record from Favorites(6195) | Primo Software | 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. |
| "My account" feature in Primo shows other institutions even if no items are checked out(6363) |
| 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. |
| Ability to configure 'User not authorized in Alma' message(6310) |
| Sometimes our users attempt to login to Primo before we have created an Alma patron record for them. In these instances, when they attempt to login, they see the message ‘The User Is Not Authorized in Alma,’ which causes confusion. For a better user experience, we would like this message to be configurable so that we can direct the user to contact the library rather than leaving them stranded and wondering what Alma is. We raised as SF ticket about this issue (# 00498705) and the response was "this text is hardcoded and we currently have no plans to make this configurable." |
| Ability to pass users ID (unique identifier) to the Pay Fine link(6300) |
| We setup Pay Fine link inside Primo Back Office. We would like to pass users ID to the Pay Fine link (like use [$userID] on the link). After clicking on Pay Fine link, users are directing to the page, on which users need to log in with their ID again. Not that much user friendly. We would like to pass users ID to the Pay Fine link so that we could use users' ID to retrieve users balance from Alma and users don't need to login again , however there is no such access to user ID variable. Adding this enhancement will eliminate users' re-login process and definitely be more user-friendly. |
| Ability to search My Favorites / eShelf(6187) |
| There needs to be a way for a user to find items in a list, or to easily see/obtain the entire list. One possible solution would be a feature that allows you to export your entire list to Excel. 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. The only way to load the entire list is to scroll to the end of the page (i.e. the first ten), then scroll again to the end (the next 10), etc. until they have gone through the entire list, 10 at a time. For users with longer lists, the system performance slows down somewhere over 100 items, so it takes longer and longer to reach the end of the list. (See use case as well). |
| Ability to sort and filter records in Digital Collections at Collection and Sub-collection level(6258) |
| When viewing the records in the new Collection Discovery feature, we require the ability to sort and filter these records. We request that sort and filter options be added to collection and sub-collections display pages. For example, the sort and filter options could include: title, creator, date, material type. |
| Add Abstract Preview to Brief or Full Display(6127) |
| Add option to enable a link on the brief record that allows patrons to preview the abstract of articles before clicking into article. Summon, our previous discovery layer, has a feature to allow patrons to view the abstract of the article before clicking to go to it. This allowed them to quickly determine (from the brief result) if the article will be useful for their research without having to click into the full record or go to the article. The convenience makes researching much faster by viewing abstracts in the same view when sorting through results (much like how Google adds descriptions in their search results) vs going to a new view to see the abstract. The item details also require a scroll to view in the Full Record, which lengthens research time. Patrons liked the efficiency of weeding through records in Summon with this abstract preview option. |
| Adding information about access to e-resources on Brief Display(6345) |
| When a network of libraries does not share the same license coverages, it is possible to configure distributed access to e-resources in Alma using the IP range of corresponding libraries (through inventory groups). However, the information about which library has access to which resource is not readily available to patrons, and one has to find different workarounds to display the information on the Full Display. It would be very useful to have the possibility to add this information on the record RTA text on the brief display, namely to have the list of libraries / inventory groups whose patrons have access to the full text resource, instead of the “Online Access” link. |
| Allow for frontend enhancements to be reliably delivered to browsers without user intervention due to cached resources.(6334) |
| Freshly deployed changes are frequently not rendered because older versions of custom.js or custom.css files are cached in a user's browser. This is because frontend assets are currently deployed using a statically prescribed naming scheme (e.g. custom1.css, custom.js, etc.). In order to allow for frontend enhancements to be reliably delivered to browsers without user intervention, the package management deploy process should allow for uploading custom-named assets (e.g. custom.[hash-value].js) OR automate a cache-busting naming scheme, such as an incremental number in the filename, which would force the customxxx.js and css files to be loaded again after each deploy since an older filename would not be found in the browser cache. |
| Connect Preferred Language Setting in Alma Patron Record To Language Preference in Primo(6355) |
| Right now, when a user’s preferred language is set in Alma either manually or by SIS, it only affects the language for email correspondences generated by Alma. It does not determine the language preference in Primo, this has to be set by the user with their Primo account settings. Similarly when a user sets their preferred language in Primo, it only affects the display language in Primo. It does not determine the language preference in Alma for correspondence, this requires staff intervention. We’d like the preferred language settings in Alma and Primo to be connected so that both parts are set by either action. |
| Display item policy in item record(6519) |
| 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. |
| Enable Database A-Z functionality for Database Search in Primo VE(6233) |
| In Primo VE the Database Search no longer includes the Database A-Z listing that was available in traditional Primo. Feedback from our users and usage statistics from our website indicate that A-Z listings are our users preferred method of finding and accessing databases. We would therefore like the Database Search in Primo VE to include a Database A-Z listing in order to give our users the ability to navigate to databases using their preferred method. |
| Enable option to favour latest edition of bibliographic work to top the FRBR group(6230) |
| For when records for editions of a bibliographic work are FRBRised, customers can choose whether to display a “Generic Record” or to have a “Preferred Record” front the group in the results listing. We find the latter option to be the better solution, provided we could configure the “Preferred record” to be that of the latest edition, which we can’t today. Instead, Primo will choose the record it decides is the best quality, regardless of whether it is the latest edition or not. We want the option to set Primo to always display the latest edition of the work to 'front' the FRBR group. Whilst all editions can be found by clicking 'View all editions', we feel our students and academics will for the most part be seeking the latest edition and prefer to see that record first. |
| External Services Linking in Primo OVP.(6335) |
| Provide support in the angular UI for Institutions to add links in the Primo UI (including OvP sections) to external services for additional request options outside of the Primo environment. |
| Full integration of Syndetics enrichment content(6426) |
| Syndetic Solutions enrichment content should be indexed in Primo, to aid the retrieval of books (especially by chapter titles in TOCs) and displayed inline in the new Primo VE. Originally appeared on https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/11034849-full-integration-of-syndetics-enrichment-content |
| Improve logic for Consortial/AFN and ILL requests(6411) |
| If all holdings across the NZ are unavailable, we want to be able to suppress the option to place a Consortial loan request (ie. a resource sharing request in an automated fulfillment network), thus directing the user to ILL. |
| Improve the date filter in the New UI, to make it clearer that a user can type in the date as opposed to clicking the arrows(6231) |
| Improve date filter – the current date filter includes default ‘From’ and ‘To’ dates with up/down arrows. Although it is possible to enter dates manually this is not intuitive. We have feedback that our users think they can only use the arrows to alter the date one year at a time. We would like to see the default dates removed so users have to enter their own ‘From’ and ‘To’ dates. This would make the date filter consistent with many other search interfaces that our users will be familiar with. |
| Include offsite storage as a top-level availability facet(6295) |
| As a distinct and important category, offsite storage should be added as a top-level availability facet. |
| My Favorites: while pinning item, allow user to choose label(4462) |
| When a user pins an item to My Favorites from the search results or detail view, the item goes to My Favorites without a label. Users would like to choose the label at the time they pin it. Otherwise, they have to pin things, then go into My Favorites and go through all the things they just pinned a second time. By this time the user may not recall the specific reason they pinned it. We would like My Favorites to work similar to Pinterest and other similar tools, where the user can assign a tag/label as they are pinning, which is when they know why they want to save the item for later. If they can't do it while they are pinning, they will have to perform additional actions later to assign labels, and try to recall why they pinned the item at the earlier time. USE CASE: A user is reviewing a result list. They want to pin items that they want to use now for part 1 of a paper, and pin items that they want to use later for part 2 of a paper, which is due later in the semester. The user pins items while reviewing the result list, but cannot assign labels at that time. After pinning items from the result list, they have to go to My Favorites and add labels for items they already decided they want, and have to then remember whether they wanted them for Part 1 of their paper or Part 2. |
| Netflix-like collection discovery interface for audio-visual collections(6292) |
| As a library, I would like to offer a browsable search interface for videos and audio collections so that students have a familiar experience when searching for audio-visual materials. Ideally, the service would merge Alexander Street Press, Naxos, Kanopy, digital campus and other service provider holdings into a single browsable audio and video experience. |
| Open records in same window rather than new window when direct linking is enabled but service not available(6409) |
| When direct linking is enabled, clicking on the availability statement for a record that is exempt from direct linking (ie. No Online Access, etc.) opens the 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, the action would mimic the same behavior that occurs when direct linking is off by having the record display in an overlay (in the same window) with focus placed on the "Get it" section. |
| PrimoVE: Local fields for all MARC tags(6217) |
| Currently local Primo VE fields can only be created for a small set of MARC fields (009, 09X, 490, 5XX, 69X, and 9XX). There seems to be no reason for this limitation. ALL MARC tags should be available to use as local fields. It would be more beneficial if the mappings of fields could be configured and if the restriction on available MARC fields for local fields was lifted. Currently information we want to display may already be included in the MARC record, but either not in the field Primo VE maps to for display of that field, or not within the range of local fields. This means fields have to be unnecessarily duplicated. It would also be useful to be able to define a subfield within a mapping. |
| Proxy-API for secure traffic of web services (6296) |
| Several web services will not work within the customization framework because modern browsers introduce a security feature which will not allow externally hosted scripts to run within the web page of the primo interface. While this might be good for simple template changes to the UI, more complex $http services (two-way communication with external APIs, https to http communication, or communication on a different TCP port) require CORS to be disabled on the non-primo webservice or that an intermediary proxy service run to "translate" headers for the browser to accept the incoming data from external webservices - enabling more complex interactions between primo nui web components and external web services (like ILLiad API for example). We would like a proxy service to enable these types of web services (please see https://gpeterso.github.io/primo-show-and-tell-2017-08/#/5/5 or attached document) |
| Publicly documented Primo AngularJS services for use in AngularJS customizations(6332) |
| As a part of the Angular architecture, services are globally accessible functions. When building frontend customizations, there may be useful already-existing AngularJS services APIs that a developer can leverage. For example, a "login" service may already exist, and these functions may be of use in an institution's customizations. Currently, developers must use ad-hoc code excavation to leverage this functionality. More AngularJS services should be written in a way intended for consumption in customizations and publicly documented. This includes refactoring currently-existing services for public consumption, as well as architecting future services with public/institutional consumption in mind. |
| Show physical availability in brief display for PCI records (Primo VE only)(5909) |
| It seems that when our physical holdings are connected to a record retrieved from PCI, only the electronic availability appears in the Primo brief display. For records coming from Alma that have both electronic and physical holdings, both types of availability show in the brief display. This inconsistency is confusing to our patrons, and we'd like to see both electronic and physical availability on the brief display. |
| sticky sort order(6126) |
| the classic UI retained any changes made to the user to the sort order of results, such that a change to e.g. sort by date newest would be retained for the duration of their session. the new ui doesn't work in this way but the ability to set a sticky sort order or to be able to set an individual sort order preference on a user by user basis would be excellent. |
| Support in the Angular UI for easily integrating with external analytics platforms.(6337) |
| Institutions need the ability measure user activity in the framework of multiple complex and deeply integrated web platforms. Support in the Angular UI application to easily integrate with any of the many external Analytics platforms (such as Google Analytics, Google Tag manger, etc.) so that institutions can centrally track all events in the UI is desired. Any feature/action that is important enough to be aded to the UI, is important enough to be captured by the analytics platform. |